🏠 Home 📊 Dashboard 💧 Mempool

Ninacatcoin Blockchain

Real-Time Network Analytics & Monitoring

Live data from the Ninacatcoin testnet

Autorefresh is OFF

Tx hash: 019a9ba3217adb61e71d222dc15d0cceff4ac33f1321dbbee115313ddd5c02f0

Tx prefix hash: 17bfa5298e8f03608d6f3c86c2db48984b6429c21c8b25dfbfae6165566df3e2
Tx public key: 1c7f268e8ca1e85a69628a7e8a3a1494c633e3b3db9e18d9be4e92021a9250fa
Timestamp: 1773483126 Timestamp [UTC]: 2026-03-14 10:12:06 Age [y:d:h:m:s]: 00:002:00:39:30
Block: 972 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1449 RingCT/type: yes/0
Extra: 011c7f268e8ca1e85a69628a7e8a3a1494c633e3b3db9e18d9be4e92021a9250fa0211000000022ceb63df000000000000000000

1 output(s) for total of 16.623063326021 nia

stealth address amount amount idx tag
00: cd233869df233b80b38bcb2366a365638504560afbdb72ac5c428777c9ead25a 16.623063326021 1473 of 0 <99>

Check which outputs belong to given Ninacatcoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Ninacatcoin in this transaction

Tx private key can be obtained using get_tx_key command in ninacatcoin-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1002, "vin": [ { "gen": { "height": 972 } } ], "vout": [ { "amount": 16623063326021, "target": { "tagged_key": { "key": "cd233869df233b80b38bcb2366a365638504560afbdb72ac5c428777c9ead25a", "view_tag": "99" } } } ], "extra": [ 1, 28, 127, 38, 142, 140, 161, 232, 90, 105, 98, 138, 126, 138, 58, 20, 148, 198, 51, 227, 179, 219, 158, 24, 217, 190, 78, 146, 2, 26, 146, 80, 250, 2, 17, 0, 0, 0, 2, 44, 235, 99, 223, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): -- (1.2) | ninacatcoin version: 0.1.0.0-unknown