🏠 Home 📊 Dashboard 💧 Mempool

Ninacatcoin Blockchain

Real-Time Network Analytics & Monitoring

Live data from the Ninacatcoin testnet

Autorefresh is OFF

Tx hash: ce4488d0f9b4a2de39f3716f4bc2477ffa9cf85eb271d7521b2c5cced4e5343e

Tx prefix hash: 27aee82811905c4f074c1e8b6945d767b323ca72c0290540981bc50342daf0a9
Tx public key: 16a19b0a83420f00f1437d935b2bf17aa0a8642ab2c57a8eb198b4ffb2b03cee
Timestamp: 1773404664 Timestamp [UTC]: 2026-03-13 12:24:24 Age [y:d:h:m:s]: 00:000:06:26:08
Block: 512 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 153 RingCT/type: yes/0
Extra: 0116a19b0a83420f00f1437d935b2bf17aa0a8642ab2c57a8eb198b4ffb2b03cee0211000000059626d8b7000000000000000000

1 output(s) for total of 16.630373462003 nia

stealth address amount amount idx tag
00: f1807b6460da3d47f1aeb1224ccb27c20ccacd175eaef16196719c1ed76ae51d 16.630373462003 651 of 0 <86>

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": 542, "vin": [ { "gen": { "height": 512 } } ], "vout": [ { "amount": 16630373462003, "target": { "tagged_key": { "key": "f1807b6460da3d47f1aeb1224ccb27c20ccacd175eaef16196719c1ed76ae51d", "view_tag": "86" } } } ], "extra": [ 1, 22, 161, 155, 10, 131, 66, 15, 0, 241, 67, 125, 147, 91, 43, 241, 122, 160, 168, 100, 42, 178, 197, 122, 142, 177, 152, 180, 255, 178, 176, 60, 238, 2, 17, 0, 0, 0, 5, 150, 38, 216, 183, 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