🏠 Home 📊 Dashboard 💧 Mempool

Ninacatcoin Blockchain

Real-Time Network Analytics & Monitoring

Live data from the Ninacatcoin testnet

Autorefresh is OFF

Tx hash: 6c68cb60be07323f6b8e8c81a65309430f723e3a707ac67bf76e8faeb25fc9e6

Tx prefix hash: fd713a8ad893df5d52deaf7e95b32ef5b683086f04eca90044a722a14d5ecb91
Tx public key: 10f6f61e4e767d70eae6121550789f791bc381a20d2d3ae44a9fa2c7f75624ba
Timestamp: 1773691719 Timestamp [UTC]: 2026-03-16 20:08:39 Age [y:d:h:m:s]: 00:000:03:25:14
Block: 2693 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 95 RingCT/type: yes/0
Extra: 0110f6f61e4e767d70eae6121550789f791bc381a20d2d3ae44a9fa2c7f75624ba021100000003e6c24e35000000000000000000

1 output(s) for total of 16.595754051875 nia

stealth address amount amount idx tag
00: ac249db81fc8d27200c952672d5b3d349e069962a21a22398fb4a12622a5ae99 16.595754051875 5069 of 0 <00>

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": 2723, "vin": [ { "gen": { "height": 2693 } } ], "vout": [ { "amount": 16595754051875, "target": { "tagged_key": { "key": "ac249db81fc8d27200c952672d5b3d349e069962a21a22398fb4a12622a5ae99", "view_tag": "00" } } } ], "extra": [ 1, 16, 246, 246, 30, 78, 118, 125, 112, 234, 230, 18, 21, 80, 120, 159, 121, 27, 195, 129, 162, 13, 45, 58, 228, 74, 159, 162, 199, 247, 86, 36, 186, 2, 17, 0, 0, 0, 3, 230, 194, 78, 53, 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