🏠 Home 📊 Dashboard 💧 Mempool

Ninacatcoin Blockchain

Real-Time Network Analytics & Monitoring

Live data from the Ninacatcoin testnet

Autorefresh is OFF

Tx hash: 8e3dfb37a7655c324ee11767cb1d1cbf29edbf33f13348cb2ab2a818ac423978

Tx prefix hash: fb97fda65716e85a1998207808803f7e8e85f091afaf4c2b9c6ed974f60fb51b
Tx public key: 16182dac8874b623ef0770bbd8cceec2e5b9ef4a7d067f1e8a103e64c942020f
Timestamp: 1773510917 Timestamp [UTC]: 2026-03-14 17:55:17 Age [y:d:h:m:s]: 00:001:16:56:19
Block: 1208 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1213 RingCT/type: yes/0
Extra: 0116182dac8874b623ef0770bbd8cceec2e5b9ef4a7d067f1e8a103e64c942020f02110000001d0498e89f000000000000000000

1 output(s) for total of 16.619306451673 nia

stealth address amount amount idx tag
00: c19d007f8f0db5e2bcdc9afb9f3c38d75316731692eb1c46d1f975f6ea7ba2ee 16.619306451673 1930 of 0 <35>

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": 1238, "vin": [ { "gen": { "height": 1208 } } ], "vout": [ { "amount": 16619306451673, "target": { "tagged_key": { "key": "c19d007f8f0db5e2bcdc9afb9f3c38d75316731692eb1c46d1f975f6ea7ba2ee", "view_tag": "35" } } } ], "extra": [ 1, 22, 24, 45, 172, 136, 116, 182, 35, 239, 7, 112, 187, 216, 204, 238, 194, 229, 185, 239, 74, 125, 6, 127, 30, 138, 16, 62, 100, 201, 66, 2, 15, 2, 17, 0, 0, 0, 29, 4, 152, 232, 159, 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