🏠 Home 📊 Dashboard 💧 Mempool

Ninacatcoin Blockchain

Real-Time Network Analytics & Monitoring

Live data from the Ninacatcoin testnet

Autorefresh is OFF

Tx hash: f6f040ef0050d1f4474a37cebf7d1f99656ad53bb22442c0c845ba44cbc840bf

Tx prefix hash: 0d4e27c2d12c16011d207bc8453e1845c00c26e537d1d2ef4d0a215d55384127
Tx public key: 72d9a15b7cd6c1363ee31d46a3b4bb5682709ac23642b97f5c87757a1a6be83a
Timestamp: 1773450453 Timestamp [UTC]: 2026-03-14 01:07:33 Age [y:d:h:m:s]: 00:002:09:44:03
Block: 718 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1709 RingCT/type: yes/0
Extra: 0172d9a15b7cd6c1363ee31d46a3b4bb5682709ac23642b97f5c87757a1a6be83a0211000000021f48d96d000000000000000000

1 output(s) for total of 16.627090642928 nia

stealth address amount amount idx tag
00: 6a2b39db898dbef7faa7f04cc2ca8e7ccd690e4b2a6b645f75dbd4fbac6d759d 16.627090642928 963 of 0 <f0>

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": 748, "vin": [ { "gen": { "height": 718 } } ], "vout": [ { "amount": 16627090642928, "target": { "tagged_key": { "key": "6a2b39db898dbef7faa7f04cc2ca8e7ccd690e4b2a6b645f75dbd4fbac6d759d", "view_tag": "f0" } } } ], "extra": [ 1, 114, 217, 161, 91, 124, 214, 193, 54, 62, 227, 29, 70, 163, 180, 187, 86, 130, 112, 154, 194, 54, 66, 185, 127, 92, 135, 117, 122, 26, 107, 232, 58, 2, 17, 0, 0, 0, 2, 31, 72, 217, 109, 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