🏠 Home 📊 Dashboard 💧 Mempool

Ninacatcoin Blockchain

Real-Time Network Analytics & Monitoring

Live data from the Ninacatcoin testnet

Autorefresh is OFF

Tx hash: e2b0507627eb022566370bb0c74e24b39ff31464371bbbbcab3fcdd41f0e8ec1

Tx prefix hash: a9ff8f40693c4ed5d4b24b958edca3c19de04c3cc1b2f1f620dad7a58335ad69
Tx public key: 246a20310b813b929826e0f9ad75845dcb93a63aaf4fdc2d7429a81c8ff1203a
Timestamp: 1773600610 Timestamp [UTC]: 2026-03-15 18:50:10 Age [y:d:h:m:s]: 00:000:16:01:26
Block: 1924 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 500 RingCT/type: yes/0
Extra: 01246a20310b813b929826e0f9ad75845dcb93a63aaf4fdc2d7429a81c8ff1203a0211000000052549f8bb000000000000000000

1 output(s) for total of 16.607929992117 nia

stealth address amount amount idx tag
00: 917ada1e508f0f5bade2f9c892f4d2f42cefd79cef500994446d2bdfe647b2d9 16.607929992117 3460 of 0 <6a>

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": 1954, "vin": [ { "gen": { "height": 1924 } } ], "vout": [ { "amount": 16607929992117, "target": { "tagged_key": { "key": "917ada1e508f0f5bade2f9c892f4d2f42cefd79cef500994446d2bdfe647b2d9", "view_tag": "6a" } } } ], "extra": [ 1, 36, 106, 32, 49, 11, 129, 59, 146, 152, 38, 224, 249, 173, 117, 132, 93, 203, 147, 166, 58, 175, 79, 220, 45, 116, 41, 168, 28, 143, 241, 32, 58, 2, 17, 0, 0, 0, 5, 37, 73, 248, 187, 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