🏠 Home 📊 Dashboard 💧 Mempool

Ninacatcoin Blockchain

Real-Time Network Analytics & Monitoring

Live data from the Ninacatcoin testnet

Autorefresh is OFF

Tx hash: 1bfde49baed47c918360176eb177b36c0c37b30e0232c68487518a66a50f7471

Tx prefix hash: cc04af9c3679cb2f097e821c48bf93c4e68f0ce918a0a87796ab2e9def8325fb
Tx public key: 12d6eb2f294c24647fa3fc171ae4d8ceb19b2a80cc7b572c2e3fe4fde47fce5e
Timestamp: 1773479024 Timestamp [UTC]: 2026-03-14 09:03:44 Age [y:d:h:m:s]: 00:002:01:47:52
Block: 934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1490 RingCT/type: yes/0
Extra: 0112d6eb2f294c24647fa3fc171ae4d8ceb19b2a80cc7b572c2e3fe4fde47fce5e0211000000015077f391000000000000000000

1 output(s) for total of 16.625876094511 nia

stealth address amount amount idx tag
00: e43e289194b7ceb141f48c65337f3cf43cbbf052e85ff0e8c961d2dc16750508 16.625876094511 1401 of 0 <3a>

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": 964, "vin": [ { "gen": { "height": 934 } } ], "vout": [ { "amount": 16625876094511, "target": { "tagged_key": { "key": "e43e289194b7ceb141f48c65337f3cf43cbbf052e85ff0e8c961d2dc16750508", "view_tag": "3a" } } } ], "extra": [ 1, 18, 214, 235, 47, 41, 76, 36, 100, 127, 163, 252, 23, 26, 228, 216, 206, 177, 155, 42, 128, 204, 123, 87, 44, 46, 63, 228, 253, 228, 127, 206, 94, 2, 17, 0, 0, 0, 1, 80, 119, 243, 145, 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