🏠 Home 📊 Dashboard 💧 Mempool

Ninacatcoin Blockchain

Real-Time Network Analytics & Monitoring

Live data from the Ninacatcoin testnet

Autorefresh is OFF

Tx hash: a6940bfda7869324f6c4d732d57f9e9922eb0137ccb31d358b8f55229cb8e29b

Tx prefix hash: f14510c352d134839cf2a9ef00ce3ffcf76713002ee82c5435acf8422ac8e7cf
Tx public key: cb3debe6a820e734f7cc1d903a57b3f5b0e543e976503ec05a093faf86f3de38
Timestamp: 1774208714 Timestamp [UTC]: 2026-03-22 19:45:14 Age [y:d:h:m:s]: 00:000:16:04:03
Block: 6113 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 100 RingCT/type: yes/0
Extra: 01cb3debe6a820e734f7cc1d903a57b3f5b0e543e976503ec05a093faf86f3de3802110000000104e6a887000000000000000000

1 output(s) for total of 16.542039250264 nia

stealth address amount amount idx tag
00: fe9cdbc9f6a97d78f26a2b715a086e96fe46d79fdee45b28eb7141280b9af8bd 16.542039250264 9180 of 0 <17>

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": 6143, "vin": [ { "gen": { "height": 6113 } } ], "vout": [ { "amount": 16542039250264, "target": { "tagged_key": { "key": "fe9cdbc9f6a97d78f26a2b715a086e96fe46d79fdee45b28eb7141280b9af8bd", "view_tag": "17" } } } ], "extra": [ 1, 203, 61, 235, 230, 168, 32, 231, 52, 247, 204, 29, 144, 58, 87, 179, 245, 176, 229, 67, 233, 118, 80, 62, 192, 90, 9, 63, 175, 134, 243, 222, 56, 2, 17, 0, 0, 0, 1, 4, 230, 168, 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