🏠 Home 📊 Dashboard 💧 Mempool

Ninacatcoin Blockchain

Real-Time Network Analytics & Monitoring

Live data from the Ninacatcoin testnet

Autorefresh is OFF

Tx hash: 8d64138881d75b68ad79095fd90e3ad91c48c8af807574ecb2001694f46b61e9

Tx prefix hash: 3ac77ae09b43dd600533202ab09ea03e7b0974e40f0ea88d1552797a5f01d35a
Tx public key: b49e1f7ca0ae275d97ec06aafeb3d9554db750fa6e0fec2fa6983daa303e326e
Timestamp: 1773892801 Timestamp [UTC]: 2026-03-19 04:00:01 Age [y:d:h:m:s]: 00:002:07:36:22
Block: 4223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 383 RingCT/type: yes/0
Extra: 01b49e1f7ca0ae275d97ec06aafeb3d9554db750fa6e0fec2fa6983daa303e326e021100000001172281c5000000000000000000

1 output(s) for total of 16.568410762301 nia

stealth address amount amount idx tag
00: 92f37c1ff5e5def0e31a1da08e691bd74f888680da0ff97db45c5eba2b1c922b 16.568410762301 7261 of 0 <af>

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": 4253, "vin": [ { "gen": { "height": 4223 } } ], "vout": [ { "amount": 16568410762301, "target": { "tagged_key": { "key": "92f37c1ff5e5def0e31a1da08e691bd74f888680da0ff97db45c5eba2b1c922b", "view_tag": "af" } } } ], "extra": [ 1, 180, 158, 31, 124, 160, 174, 39, 93, 151, 236, 6, 170, 254, 179, 217, 85, 77, 183, 80, 250, 110, 15, 236, 47, 166, 152, 61, 170, 48, 62, 50, 110, 2, 17, 0, 0, 0, 1, 23, 34, 129, 197, 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