🏠 Home 📊 Dashboard 💧 Mempool

Ninacatcoin Blockchain

Real-Time Network Analytics & Monitoring

Live data from the Ninacatcoin testnet

Autorefresh is OFF

Tx hash: 17bf4b0569181a99e2441cceb28db33f3666b3433bf154c141171235d5a450b8

Tx prefix hash: 315f1386ae7e98df47ec76982f9cb632326fcac641e376f50307ffc6a3080e3e
Tx public key: 82d459a3b29fe7a35b5a2f31757262d4df594708f233504d6de31a6f281f4ba4
Timestamp: 1773730899 Timestamp [UTC]: 2026-03-17 07:01:39 Age [y:d:h:m:s]: 00:004:04:46:38
Block: 2999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1607 RingCT/type: yes/0
Extra: 0182d459a3b29fe7a35b5a2f31757262d4df594708f233504d6de31a6f281f4ba4021100000001d5ea8798000000000000000000

1 output(s) for total of 16.590911598373 nia

stealth address amount amount idx tag
00: 4cf0addd99fe5c90cf7e76a2aa0367f9b3a934c0f1b7534d6fd70557f8bf111a 16.590911598373 5436 of 0 <8f>

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": 3029, "vin": [ { "gen": { "height": 2999 } } ], "vout": [ { "amount": 16590911598373, "target": { "tagged_key": { "key": "4cf0addd99fe5c90cf7e76a2aa0367f9b3a934c0f1b7534d6fd70557f8bf111a", "view_tag": "8f" } } } ], "extra": [ 1, 130, 212, 89, 163, 178, 159, 231, 163, 91, 90, 47, 49, 117, 114, 98, 212, 223, 89, 71, 8, 242, 51, 80, 77, 109, 227, 26, 111, 40, 31, 75, 164, 2, 17, 0, 0, 0, 1, 213, 234, 135, 152, 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