🏠 Home 📊 Dashboard 💧 Mempool

Ninacatcoin Blockchain

Real-Time Network Analytics & Monitoring

Live data from the Ninacatcoin testnet

Autorefresh is OFF

Tx hash: dd45810005abed31b110bbe64e59302879e59da4f22c7a308173ffbaba0016d9

Tx prefix hash: ff82d89aa3bf506fb0b1d095d09474e9caf2cd5bcef424382d20c59443ee7fa4
Tx public key: ef8e46f047ba853c1b8a245ef9d51c0a341f174605eb9093b9964cfd81e3b2f3
Timestamp: 1773502950 Timestamp [UTC]: 2026-03-14 15:42:30 Age [y:d:h:m:s]: 00:001:19:09:06
Block: 1139 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1283 RingCT/type: yes/0
Extra: 01ef8e46f047ba853c1b8a245ef9d51c0a341f174605eb9093b9964cfd81e3b2f30211000000040ae69111000000000000000000

1 output(s) for total of 16.620400134646 nia

stealth address amount amount idx tag
00: b8a31a7dc3ecefc71556274969c2e0dcc501beaabfc6b9d707aa5382b0d0a952 16.620400134646 1802 of 0 <cb>

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": 1169, "vin": [ { "gen": { "height": 1139 } } ], "vout": [ { "amount": 16620400134646, "target": { "tagged_key": { "key": "b8a31a7dc3ecefc71556274969c2e0dcc501beaabfc6b9d707aa5382b0d0a952", "view_tag": "cb" } } } ], "extra": [ 1, 239, 142, 70, 240, 71, 186, 133, 60, 27, 138, 36, 94, 249, 213, 28, 10, 52, 31, 23, 70, 5, 235, 144, 147, 185, 150, 76, 253, 129, 227, 178, 243, 2, 17, 0, 0, 0, 4, 10, 230, 145, 17, 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