🏠 Home 📊 Dashboard 💧 Mempool

Ninacatcoin Blockchain

Real-Time Network Analytics & Monitoring

Live data from the Ninacatcoin testnet

Autorefresh is OFF

Tx hash: efa692c104f522c4ed62730e3aa45bd4b23112e5043186249aa44f982e841ab3

Tx prefix hash: 825bc9b35c7abb852aef2b8e6b616f08d7f0f9858acda615361438d1f7910de5
Tx public key: 3d5d8184a44f306702165aa9fa90eebcd042662ffdabfb1f05194591c6e6797e
Timestamp: 1773567127 Timestamp [UTC]: 2026-03-15 09:32:07 Age [y:d:h:m:s]: 00:001:01:19:29
Block: 1656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 774 RingCT/type: yes/0
Extra: 013d5d8184a44f306702165aa9fa90eebcd042662ffdabfb1f05194591c6e6797e021100000004fd8f4d87000000000000000000

1 output(s) for total of 16.612207130858 nia

stealth address amount amount idx tag
00: 66b326881f5a2a6ff9077b7d3e646e10cd7b54f2e51901854ac54fb849fe50f9 16.612207130858 2902 of 0 <f2>

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": 1686, "vin": [ { "gen": { "height": 1656 } } ], "vout": [ { "amount": 16612207130858, "target": { "tagged_key": { "key": "66b326881f5a2a6ff9077b7d3e646e10cd7b54f2e51901854ac54fb849fe50f9", "view_tag": "f2" } } } ], "extra": [ 1, 61, 93, 129, 132, 164, 79, 48, 103, 2, 22, 90, 169, 250, 144, 238, 188, 208, 66, 102, 47, 253, 171, 251, 31, 5, 25, 69, 145, 198, 230, 121, 126, 2, 17, 0, 0, 0, 4, 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