🏠 Home 📊 Dashboard 💧 Mempool

Ninacatcoin Blockchain

Real-Time Network Analytics & Monitoring

Live data from the Ninacatcoin testnet

Autorefresh is OFF

Tx hash: e1f634e0abaea8b8e6c2117930131b648cc98aa5720f334075776d7a0c45e67e

Tx prefix hash: 590194c2e0884ce934bc4c68b8b1e6daf571c3cc8f22f195ae71cf92d4bb3655
Tx public key: 862c6b33024b08d10fe7fcc3e7fd174eaed96d5f5e9023d2416a8db619b87a82
Timestamp: 1773488469 Timestamp [UTC]: 2026-03-14 11:41:09 Age [y:d:h:m:s]: 00:001:23:10:27
Block: 1017 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1406 RingCT/type: yes/0
Extra: 01862c6b33024b08d10fe7fcc3e7fd174eaed96d5f5e9023d2416a8db619b87a820211000000020ae69111000000000000000000

1 output(s) for total of 16.626401914184 nia

stealth address amount amount idx tag
00: d82b43e5fe4e8868223a486ead63d270a92c0a62b9a2099915c68dadd6869263 16.626401914184 1560 of 0 <0c>

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": 1047, "vin": [ { "gen": { "height": 1017 } } ], "vout": [ { "amount": 16626401914184, "target": { "tagged_key": { "key": "d82b43e5fe4e8868223a486ead63d270a92c0a62b9a2099915c68dadd6869263", "view_tag": "0c" } } } ], "extra": [ 1, 134, 44, 107, 51, 2, 75, 8, 209, 15, 231, 252, 195, 231, 253, 23, 78, 174, 217, 109, 95, 94, 144, 35, 210, 65, 106, 141, 182, 25, 184, 122, 130, 2, 17, 0, 0, 0, 2, 10, 230, 145, 17, 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