🏠 Home 📊 Dashboard 💧 Mempool

Ninacatcoin Blockchain

Real-Time Network Analytics & Monitoring

Live data from the Ninacatcoin testnet

Autorefresh is OFF

Tx hash: 47c7c43657d0dfd87f96df414c5be9aa797d6868845cba5864b1fa53fc32f568

Tx prefix hash: f47b0ca3f7dec9610566858be53dc86baef0ed2f053e8e0621b1e5da30836c5d
Tx public key: 02c663d3a23c3b37c4b681084fb13c59a7ec7e64cb385279ea0fbcd5709f196a
Timestamp: 1773783202 Timestamp [UTC]: 2026-03-17 21:33:22 Age [y:d:h:m:s]: 00:003:14:03:01
Block: 3357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1249 RingCT/type: yes/0
Extra: 0102c663d3a23c3b37c4b681084fb13c59a7ec7e64cb385279ea0fbcd5709f196a021100000001774cb830000000000000000000

1 output(s) for total of 16.582100434569 nia

stealth address amount amount idx tag
00: 652c1a3f26fcd1f049cde5eb332bb50522f42014472d7150513268cf34ad3465 16.582100434569 5909 of 0 <84>

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": 3387, "vin": [ { "gen": { "height": 3357 } } ], "vout": [ { "amount": 16582100434569, "target": { "tagged_key": { "key": "652c1a3f26fcd1f049cde5eb332bb50522f42014472d7150513268cf34ad3465", "view_tag": "84" } } } ], "extra": [ 1, 2, 198, 99, 211, 162, 60, 59, 55, 196, 182, 129, 8, 79, 177, 60, 89, 167, 236, 126, 100, 203, 56, 82, 121, 234, 15, 188, 213, 112, 159, 25, 106, 2, 17, 0, 0, 0, 1, 119, 76, 184, 48, 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