🏠 Home 📊 Dashboard 💧 Mempool

Ninacatcoin Blockchain

Real-Time Network Analytics & Monitoring

Live data from the Ninacatcoin testnet

Autorefresh is OFF

Tx hash: a1e4914a2ec513925194065a650d6c9a3c56681f0efd6fe75a1f43204e1fdbc8

Tx prefix hash: d249cd61134e2412dbf3ed6611a94d17b82f2404ce4bb0d646956a365a4033bd
Tx public key: 7c26ee26e13d14d315a2027d80f2dbe596f2ea81041fc8f632251ff462e7938d
Timestamp: 1773744717 Timestamp [UTC]: 2026-03-17 10:51:57 Age [y:d:h:m:s]: 00:004:00:54:52
Block: 3113 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1493 RingCT/type: yes/0
Extra: 017c26ee26e13d14d315a2027d80f2dbe596f2ea81041fc8f632251ff462e7938d02110000000370303023000000000000000000

1 output(s) for total of 16.585959595145 nia

stealth address amount amount idx tag
00: fa6a7621f860d7ee9d242e7c85ae4c34ce75ee4b720270a3c2bae631fb9109cb 16.585959595145 5577 of 0 <e2>

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": 3143, "vin": [ { "gen": { "height": 3113 } } ], "vout": [ { "amount": 16585959595145, "target": { "tagged_key": { "key": "fa6a7621f860d7ee9d242e7c85ae4c34ce75ee4b720270a3c2bae631fb9109cb", "view_tag": "e2" } } } ], "extra": [ 1, 124, 38, 238, 38, 225, 61, 20, 211, 21, 162, 2, 125, 128, 242, 219, 229, 150, 242, 234, 129, 4, 31, 200, 246, 50, 37, 31, 244, 98, 231, 147, 141, 2, 17, 0, 0, 0, 3, 112, 48, 48, 35, 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