🏠 Home 📊 Dashboard 💧 Mempool

Ninacatcoin Blockchain

Real-Time Network Analytics & Monitoring

Live data from the Ninacatcoin testnet

Autorefresh is OFF

Tx hash: 270c7f4df1fcdec569cc36a405dabea317d532d9857552360f7c6f2735382df1

Tx prefix hash: d48245c21c404543fdefcba9bbd2a9c83dd3c1245db5525dbe178d0c3c064931
Tx public key: bd44c2770f4a9c117f13abe9cb57c33053d082c11d01aa1f5f8012b0492c807c
Timestamp: 1773754378 Timestamp [UTC]: 2026-03-17 13:32:58 Age [y:d:h:m:s]: 00:003:22:15:19
Block: 3197 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1409 RingCT/type: yes/0
Extra: 01bd44c2770f4a9c117f13abe9cb57c33053d082c11d01aa1f5f8012b0492c807c02110000000468e30af7000000000000000000

1 output(s) for total of 16.584630927659 nia

stealth address amount amount idx tag
00: 36e25f31b60a4a2cb2972fee9809e060a153cfb578c68d0458b311433f5f704c 16.584630927659 5703 of 0 <15>

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": 3227, "vin": [ { "gen": { "height": 3197 } } ], "vout": [ { "amount": 16584630927659, "target": { "tagged_key": { "key": "36e25f31b60a4a2cb2972fee9809e060a153cfb578c68d0458b311433f5f704c", "view_tag": "15" } } } ], "extra": [ 1, 189, 68, 194, 119, 15, 74, 156, 17, 127, 19, 171, 233, 203, 87, 195, 48, 83, 208, 130, 193, 29, 1, 170, 31, 95, 128, 18, 176, 73, 44, 128, 124, 2, 17, 0, 0, 0, 4, 104, 227, 10, 247, 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