🏠 Home 📊 Dashboard 💧 Mempool

Ninacatcoin Blockchain

Real-Time Network Analytics & Monitoring

Live data from the Ninacatcoin testnet

Autorefresh is OFF

Tx hash: 14884327863ae458c3f75b485b1856ecacb2e673c1a7528a349504729f104b9c

Tx prefix hash: 4f2c7c1cc681353fe4ab5628f000245e87812b9fc5227aefedd67b771dcf3190
Tx public key: 4c0229f87e7d8cdb3676d942389768a940d2f0611a48e1cf985e39240b15f1bf
Timestamp: 1773541227 Timestamp [UTC]: 2026-03-15 02:20:27 Age [y:d:h:m:s]: 00:001:10:02:18
Block: 1463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1008 RingCT/type: yes/0
Extra: 014c0229f87e7d8cdb3676d942389768a940d2f0611a48e1cf985e39240b15f1bf021100000002fd8f4d87000000000000000000

1 output(s) for total of 16.618639176673 nia

stealth address amount amount idx tag
00: e5d5eb1aad0a3a8f0761c1852053bdd5082a167316e4f911b5532e9cf4adca3c 16.618639176673 2465 of 0 <4e>

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": 1493, "vin": [ { "gen": { "height": 1463 } } ], "vout": [ { "amount": 16618639176673, "target": { "tagged_key": { "key": "e5d5eb1aad0a3a8f0761c1852053bdd5082a167316e4f911b5532e9cf4adca3c", "view_tag": "4e" } } } ], "extra": [ 1, 76, 2, 41, 248, 126, 125, 140, 219, 54, 118, 217, 66, 56, 151, 104, 169, 64, 210, 240, 97, 26, 72, 225, 207, 152, 94, 57, 36, 11, 21, 241, 191, 2, 17, 0, 0, 0, 2, 253, 143, 77, 135, 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