🏠 Home 📊 Dashboard 💧 Mempool

Ninacatcoin Blockchain

Real-Time Network Analytics & Monitoring

Live data from the Ninacatcoin testnet

Autorefresh is OFF

Tx hash: 7677b4cca91e00c967d2a7a3152893a327719ce89f90693b968821c9b52dd5e5

Tx prefix hash: ab14df8727714ab831d5d0dc6ddfd10a8fd07ad998f773dcb1f57ba151a40e44
Tx public key: 0ea01a274e161c4c19f12a72a0b062a0446bdf6de07c90adcf8c71611a4ee04f
Timestamp: 1773490758 Timestamp [UTC]: 2026-03-14 12:19:18 Age [y:d:h:m:s]: 00:001:22:32:18
Block: 1039 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1386 RingCT/type: yes/0
Extra: 010ea01a274e161c4c19f12a72a0b062a0446bdf6de07c90adcf8c71611a4ee04f0211000000020ae69111000000000000000000

1 output(s) for total of 16.621985313482 nia

stealth address amount amount idx tag
00: 68d7e75e8216f8edf511ba0bf5e165b454222e887535ecef9a45fd2504548ecb 16.621985313482 1602 of 0 <61>

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": 1069, "vin": [ { "gen": { "height": 1039 } } ], "vout": [ { "amount": 16621985313482, "target": { "tagged_key": { "key": "68d7e75e8216f8edf511ba0bf5e165b454222e887535ecef9a45fd2504548ecb", "view_tag": "61" } } } ], "extra": [ 1, 14, 160, 26, 39, 78, 22, 28, 76, 25, 241, 42, 114, 160, 176, 98, 160, 68, 107, 223, 109, 224, 124, 144, 173, 207, 140, 113, 97, 26, 78, 224, 79, 2, 17, 0, 0, 0, 2, 10, 230, 145, 17, 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