🏠 Home 📊 Dashboard 💧 Mempool

Ninacatcoin Blockchain

Real-Time Network Analytics & Monitoring

Live data from the Ninacatcoin testnet

Autorefresh is OFF

Tx hash: 67b5d57fb337ccf5e765042a7dd52cdec79679e388d3c7b9429dada3427fe193

Tx prefix hash: 73bc1346cd06acf04980bef59d9bda0a050fc34f9650ca26094ce2f4f148585e
Tx public key: d432f121457f4a3b786a76ef14f38c5a0bc1aa3725a0f4d87a3f1866be51028e
Timestamp: 1773829316 Timestamp [UTC]: 2026-03-18 10:21:56 Age [y:d:h:m:s]: 00:003:04:23:03
Block: 3766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 840 RingCT/type: yes/0
Extra: 01d432f121457f4a3b786a76ef14f38c5a0bc1aa3725a0f4d87a3f1866be51028e0211000000028243bf6b000000000000000000

1 output(s) for total of 16.575633618911 nia

stealth address amount amount idx tag
00: 9dc29649ccbc31168c562d477c30d1c1d252f83dc872218c6556a2067d123308 16.575633618911 6432 of 0 <e5>

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": 3796, "vin": [ { "gen": { "height": 3766 } } ], "vout": [ { "amount": 16575633618911, "target": { "tagged_key": { "key": "9dc29649ccbc31168c562d477c30d1c1d252f83dc872218c6556a2067d123308", "view_tag": "e5" } } } ], "extra": [ 1, 212, 50, 241, 33, 69, 127, 74, 59, 120, 106, 118, 239, 20, 243, 140, 90, 11, 193, 170, 55, 37, 160, 244, 216, 122, 63, 24, 102, 190, 81, 2, 142, 2, 17, 0, 0, 0, 2, 130, 67, 191, 107, 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