🏠 Home 📊 Dashboard 💧 Mempool

Ninacatcoin Blockchain

Real-Time Network Analytics & Monitoring

Live data from the Ninacatcoin testnet

Autorefresh is OFF

Tx hash: ffe39a5a9a8552e907c771d41eacd12b5d8f3a5de78a8d73bb132634c6f02ce9

Tx prefix hash: f210ad0ff586a1741bc6f0fd7117a9d37327e0f57d99c981219a07a0a7835056
Tx public key: ec05670021a65448d7a964d769ed92fb6a9089d2eab643d9b5cd1c0853d8714e
Timestamp: 1774222631 Timestamp [UTC]: 2026-03-22 23:37:11 Age [y:d:h:m:s]: 00:000:11:12:06
Block: 6212 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1 RingCT/type: yes/0
Extra: 01ec05670021a65448d7a964d769ed92fb6a9089d2eab643d9b5cd1c0853d8714e021100000001abc29710000000000000000000

1 output(s) for total of 16.539357804764 nia

stealth address amount amount idx tag
00: 5603e0356e2d64eaf85f1d7a9effc6edd357d30ab16d9f7462e958ca01322105 16.539357804764 9323 of 0 <03>

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": 6242, "vin": [ { "gen": { "height": 6212 } } ], "vout": [ { "amount": 16539357804764, "target": { "tagged_key": { "key": "5603e0356e2d64eaf85f1d7a9effc6edd357d30ab16d9f7462e958ca01322105", "view_tag": "03" } } } ], "extra": [ 1, 236, 5, 103, 0, 33, 166, 84, 72, 215, 169, 100, 215, 105, 237, 146, 251, 106, 144, 137, 210, 234, 182, 67, 217, 181, 205, 28, 8, 83, 216, 113, 78, 2, 17, 0, 0, 0, 1, 171, 194, 151, 16, 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