🏠 Home 📊 Dashboard 💧 Mempool

Ninacatcoin Blockchain

Real-Time Network Analytics & Monitoring

Live data from the Ninacatcoin testnet

Autorefresh is OFF

Tx hash: 98ae5f993e67c2364ca5b8deb6936965535542342d0fbea5fa9877e0ff23115b

Tx prefix hash: 55e68918a569fa33d634e5b3d934d64afcdfa72af826fe517cb3be0e4426a22b
Tx public key: c6dc47b7a3d698f7301462c04398c5ceb6f3f040c14b2867f7b9e27bc248f978
Timestamp: 1773419583 Timestamp [UTC]: 2026-03-13 16:33:03 Age [y:d:h:m:s]: 00:000:03:22:41
Block: 621 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 48 RingCT/type: yes/0
Extra: 01c6dc47b7a3d698f7301462c04398c5ceb6f3f040c14b2867f7b9e27bc248f978021100000002d771133f000000000000000000

1 output(s) for total of 16.628628957056 nia

stealth address amount amount idx tag
00: 372309f6cb83a08e1ea6345fc3ac2858d032f6d93791e869600af3165525c3df 16.628628957056 760 of 0 <06>

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": 651, "vin": [ { "gen": { "height": 621 } } ], "vout": [ { "amount": 16628628957056, "target": { "tagged_key": { "key": "372309f6cb83a08e1ea6345fc3ac2858d032f6d93791e869600af3165525c3df", "view_tag": "06" } } } ], "extra": [ 1, 198, 220, 71, 183, 163, 214, 152, 247, 48, 20, 98, 192, 67, 152, 197, 206, 182, 243, 240, 64, 193, 75, 40, 103, 247, 185, 226, 123, 194, 72, 249, 120, 2, 17, 0, 0, 0, 2, 215, 113, 19, 63, 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