🏠 Home 📊 Dashboard 💧 Mempool

Ninacatcoin Blockchain

Real-Time Network Analytics & Monitoring

Live data from the Ninacatcoin testnet

Autorefresh is OFF

Tx hash: 3971c096268293f2bd38e472e51864d8fdf5d676fc728d45ca14c90424a441bd

Tx prefix hash: e87a25999bb6fcb403032a7aff6d3028ee9896a88df3e0a482001fa6797f56c7
Tx public key: 2d420b922c4e17be91a3de3f48764e5e3b0f8f8abbf043830d6cf0d0f52fc5f0
Timestamp: 1773664977 Timestamp [UTC]: 2026-03-16 12:42:57 Age [y:d:h:m:s]: 00:000:03:52:50
Block: 2480 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 115 RingCT/type: yes/0
Extra: 012d420b922c4e17be91a3de3f48764e5e3b0f8f8abbf043830d6cf0d0f52fc5f0021100000001fb89fa23000000000000000000

1 output(s) for total of 16.599125707047 nia

stealth address amount amount idx tag
00: 41c67a8db04dd894e910d0c9f8474408bb6cf9973f63d7191cdeb6ea0db1808b 16.599125707047 4726 of 0 <9c>

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": 2510, "vin": [ { "gen": { "height": 2480 } } ], "vout": [ { "amount": 16599125707047, "target": { "tagged_key": { "key": "41c67a8db04dd894e910d0c9f8474408bb6cf9973f63d7191cdeb6ea0db1808b", "view_tag": "9c" } } } ], "extra": [ 1, 45, 66, 11, 146, 44, 78, 23, 190, 145, 163, 222, 63, 72, 118, 78, 94, 59, 15, 143, 138, 187, 240, 67, 131, 13, 108, 240, 208, 245, 47, 197, 240, 2, 17, 0, 0, 0, 1, 251, 137, 250, 35, 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