🏠 Home 📊 Dashboard 💧 Mempool

Ninacatcoin Blockchain

Real-Time Network Analytics & Monitoring

Live data from the Ninacatcoin testnet

Autorefresh is OFF

Tx hash: 56cc6104f1138ce09709d5bdfa7f40c3d7deaac0811e196f74f27f22ea25b81c

Tx prefix hash: 6837b1a06d2454213d88293d2958e523acba14fdd4955d0e20d7f69aef63c78b
Tx public key: 454d8c49cccccfeca0a85c5d49df57d425fd7882440d58cb31d4a517c5339f32
Timestamp: 1773750725 Timestamp [UTC]: 2026-03-17 12:32:05 Age [y:d:h:m:s]: 00:004:00:41:42
Block: 3162 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1444 RingCT/type: yes/0
Extra: 01454d8c49cccccfeca0a85c5d49df57d425fd7882440d58cb31d4a517c5339f3202110000000256cca560000000000000000000

1 output(s) for total of 16.585184523237 nia

stealth address amount amount idx tag
00: 4a6d90890100dd4fcaf8944728cd959f5907d0d936ccd08956e22ed319146b6f 16.585184523237 5654 of 0 <b0>

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": 3192, "vin": [ { "gen": { "height": 3162 } } ], "vout": [ { "amount": 16585184523237, "target": { "tagged_key": { "key": "4a6d90890100dd4fcaf8944728cd959f5907d0d936ccd08956e22ed319146b6f", "view_tag": "b0" } } } ], "extra": [ 1, 69, 77, 140, 73, 204, 204, 207, 236, 160, 168, 92, 93, 73, 223, 87, 212, 37, 253, 120, 130, 68, 13, 88, 203, 49, 212, 165, 23, 197, 51, 159, 50, 2, 17, 0, 0, 0, 2, 86, 204, 165, 96, 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