🏠 Home 📊 Dashboard 💧 Mempool

Ninacatcoin Blockchain

Real-Time Network Analytics & Monitoring

Live data from the Ninacatcoin testnet

Autorefresh is OFF

Tx hash: 66ff42cf2db37ff8385d799786b154b7fcbd8a0b73a4879e82bdf339c032a3f1

Tx prefix hash: 108445156720b6bb18602b6ef951a8c49b41cec1a5ab89d9769f01a2023a9458
Tx public key: f4b9527cd9f632fdb8ae01c4740b58f1da2a0cd1072917ae7f809d9d4bbb08b7
Timestamp: 1773849573 Timestamp [UTC]: 2026-03-18 15:59:33 Age [y:d:h:m:s]: 00:002:21:14:14
Block: 3929 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 677 RingCT/type: yes/0
Extra: 01f4b9527cd9f632fdb8ae01c4740b58f1da2a0cd1072917ae7f809d9d4bbb08b70211000000048243bf6b000000000000000000

1 output(s) for total of 16.573057079338 nia

stealth address amount amount idx tag
00: 4354a6e34bff9209637425ea0fbc12a5a845e8b29afbc3cb23dfe662937d1dab 16.573057079338 6696 of 0 <37>

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": 3959, "vin": [ { "gen": { "height": 3929 } } ], "vout": [ { "amount": 16573057079338, "target": { "tagged_key": { "key": "4354a6e34bff9209637425ea0fbc12a5a845e8b29afbc3cb23dfe662937d1dab", "view_tag": "37" } } } ], "extra": [ 1, 244, 185, 82, 124, 217, 246, 50, 253, 184, 174, 1, 196, 116, 11, 88, 241, 218, 42, 12, 209, 7, 41, 23, 174, 127, 128, 157, 157, 75, 187, 8, 183, 2, 17, 0, 0, 0, 4, 130, 67, 191, 107, 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