🏠 Home 📊 Dashboard 💧 Mempool

Ninacatcoin Blockchain

Real-Time Network Analytics & Monitoring

Live data from the Ninacatcoin testnet

Autorefresh is OFF

Tx hash: d67ee267eda2feff13fdaa9f1502fb12184e41bc70a906124f1b34e904bdb7fd

Tx prefix hash: f462aa7471a88d14b23a2da80ed8b4179f542ac7df89bf14eac2ac9b0107b7a4
Tx public key: b264317ddb6d5d5857aa360ec9c13cdbae04145bd5b0674e51ce5dc814a07568
Timestamp: 1773625805 Timestamp [UTC]: 2026-03-16 01:50:05 Age [y:d:h:m:s]: 00:000:10:32:40
Block: 2151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 321 RingCT/type: yes/0
Extra: 01b264317ddb6d5d5857aa360ec9c13cdbae04145bd5b0674e51ce5dc814a07568021100000005a79055a0000000000000000000

1 output(s) for total of 16.604334877308 nia

stealth address amount amount idx tag
00: b239c5336d366047d5a42a7862f22d9826f2eaf59c7cfe7d3c8f9b4cd3f3d6dc 16.604334877308 3942 of 0 <45>

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": 2181, "vin": [ { "gen": { "height": 2151 } } ], "vout": [ { "amount": 16604334877308, "target": { "tagged_key": { "key": "b239c5336d366047d5a42a7862f22d9826f2eaf59c7cfe7d3c8f9b4cd3f3d6dc", "view_tag": "45" } } } ], "extra": [ 1, 178, 100, 49, 125, 219, 109, 93, 88, 87, 170, 54, 14, 201, 193, 60, 219, 174, 4, 20, 91, 213, 176, 103, 78, 81, 206, 93, 200, 20, 160, 117, 104, 2, 17, 0, 0, 0, 5, 167, 144, 85, 160, 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