🏠 Home 📊 Dashboard 💧 Mempool

Ninacatcoin Blockchain

Real-Time Network Analytics & Monitoring

Live data from the Ninacatcoin testnet

Autorefresh is OFF

Tx hash: f4e1e6721d567f123375958ff5f6a7a1d1b3d5345e6bcefa0791a2caad551625

Tx prefix hash: 835ba897e4a73a21271357a7b61cf4eb478513529d9bccd0fa9484dc749c0e37
Tx public key: 17ea780f34c9b10756ccb37886468dc33427eb4e7fd591152c222946f97f6d43
Timestamp: 1773707014 Timestamp [UTC]: 2026-03-17 00:23:34 Age [y:d:h:m:s]: 00:004:08:31:43
Block: 2811 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1795 RingCT/type: yes/0
Extra: 0117ea780f34c9b10756ccb37886468dc33427eb4e7fd591152c222946f97f6d43021100000009f76932b6000000000000000000

1 output(s) for total of 16.593886535100 nia

stealth address amount amount idx tag
00: 1b3133d56193d5e99c84439801c998c9d61332f65ea2b9c0f0a6b9cbfdff37f9 16.593886535100 5215 of 0 <96>

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": 2841, "vin": [ { "gen": { "height": 2811 } } ], "vout": [ { "amount": 16593886535100, "target": { "tagged_key": { "key": "1b3133d56193d5e99c84439801c998c9d61332f65ea2b9c0f0a6b9cbfdff37f9", "view_tag": "96" } } } ], "extra": [ 1, 23, 234, 120, 15, 52, 201, 177, 7, 86, 204, 179, 120, 134, 70, 141, 195, 52, 39, 235, 78, 127, 213, 145, 21, 44, 34, 41, 70, 249, 127, 109, 67, 2, 17, 0, 0, 0, 9, 247, 105, 50, 182, 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