🏠 Home 📊 Dashboard 💧 Mempool

Ninacatcoin Blockchain

Real-Time Network Analytics & Monitoring

Live data from the Ninacatcoin testnet

Autorefresh is OFF

Tx hash: 0b74f1a76a553c6a5854e4077d92236c5db3b4abf860d3d7f7a0d569382b043e

Tx prefix hash: bcbc1777181598e1e712b67fc7febfcce5928f0e354376a470d6ca9207fd1269
Tx public key: 334168f6064928b98faa0fe19d9a9acb0a0e66b3ab36f416e3d1a8f55bf02049
Timestamp: 1773728866 Timestamp [UTC]: 2026-03-17 06:27:46 Age [y:d:h:m:s]: 00:004:06:51:00
Block: 2982 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1624 RingCT/type: yes/0
Extra: 01334168f6064928b98faa0fe19d9a9acb0a0e66b3ab36f416e3d1a8f55bf0204902110000000570303023000000000000000000

1 output(s) for total of 16.591180580229 nia

stealth address amount amount idx tag
00: c6a8d83bcc00b04556f33f4ab69c66aa1255e75331562d352fd2c209821a7dcd 16.591180580229 5419 of 0 <26>

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": 3012, "vin": [ { "gen": { "height": 2982 } } ], "vout": [ { "amount": 16591180580229, "target": { "tagged_key": { "key": "c6a8d83bcc00b04556f33f4ab69c66aa1255e75331562d352fd2c209821a7dcd", "view_tag": "26" } } } ], "extra": [ 1, 51, 65, 104, 246, 6, 73, 40, 185, 143, 170, 15, 225, 157, 154, 154, 203, 10, 14, 102, 179, 171, 54, 244, 22, 227, 209, 168, 245, 91, 240, 32, 73, 2, 17, 0, 0, 0, 5, 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