🏠 Home 📊 Dashboard 💧 Mempool

Ninacatcoin Blockchain

Real-Time Network Analytics & Monitoring

Live data from the Ninacatcoin testnet

Autorefresh is OFF

Tx hash: 0776b2d86d561f11c51ef043003b2ed48c68f5ad6248db7df76b6357e2fc467d

Tx prefix hash: 0c860c24a05cba3525dc56d3f42525cdb19a55f09765b93717fbde393b42a3ba
Tx public key: 1c3867aaa5f8fa8aa411510ba6a9590b64d930424177874d21773afdd57e4733
Timestamp: 1773564112 Timestamp [UTC]: 2026-03-15 08:41:52 Age [y:d:h:m:s]: 00:001:03:40:53
Block: 1627 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 841 RingCT/type: yes/0
Extra: 011c3867aaa5f8fa8aa411510ba6a9590b64d930424177874d21773afdd57e4733021100000002fd8f4d87000000000000000000

1 output(s) for total of 16.612666592065 nia

stealth address amount amount idx tag
00: 6c06b7a8dbee47457a2296113e29484a0c6fcedf4d529d098b7cbdeff04b1461 16.612666592065 2843 of 0 <58>

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": 1657, "vin": [ { "gen": { "height": 1627 } } ], "vout": [ { "amount": 16612666592065, "target": { "tagged_key": { "key": "6c06b7a8dbee47457a2296113e29484a0c6fcedf4d529d098b7cbdeff04b1461", "view_tag": "58" } } } ], "extra": [ 1, 28, 56, 103, 170, 165, 248, 250, 138, 164, 17, 81, 11, 166, 169, 89, 11, 100, 217, 48, 66, 65, 119, 135, 77, 33, 119, 58, 253, 213, 126, 71, 51, 2, 17, 0, 0, 0, 2, 253, 143, 77, 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