🏠 Home 📊 Dashboard 💧 Mempool

Ninacatcoin Blockchain

Real-Time Network Analytics & Monitoring

Live data from the Ninacatcoin testnet

Autorefresh is OFF

Tx hash: 3a1c33deaf61d24b6bae9cf35a48cd8e2b0d169e6bd88f958b0f895f4f0044d8

Tx prefix hash: b1f4e49476e4ec80fddc02fc480660d3161ae89a69e9520942cb1b5ec0896f19
Tx public key: 1bdb09c09e7836a3cdde84d5d7147e2e00de633a604a8d729f168662f4a1e6bb
Timestamp: 1773734285 Timestamp [UTC]: 2026-03-17 07:58:05 Age [y:d:h:m:s]: 00:004:05:15:42
Block: 3033 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1573 RingCT/type: yes/0
Extra: 011bdb09c09e7836a3cdde84d5d7147e2e00de633a604a8d729f168662f4a1e6bb02110000000270303023000000000000000000

1 output(s) for total of 16.590373627137 nia

stealth address amount amount idx tag
00: cac3a6a12930eb748f39eac9780e43e7b5e992a573fd2743c775da2e669ee3ca 16.590373627137 5480 of 0 <85>

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": 3063, "vin": [ { "gen": { "height": 3033 } } ], "vout": [ { "amount": 16590373627137, "target": { "tagged_key": { "key": "cac3a6a12930eb748f39eac9780e43e7b5e992a573fd2743c775da2e669ee3ca", "view_tag": "85" } } } ], "extra": [ 1, 27, 219, 9, 192, 158, 120, 54, 163, 205, 222, 132, 213, 215, 20, 126, 46, 0, 222, 99, 58, 96, 74, 141, 114, 159, 22, 134, 98, 244, 161, 230, 187, 2, 17, 0, 0, 0, 2, 112, 48, 48, 35, 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