🏠 Home 📊 Dashboard 💧 Mempool

Ninacatcoin Blockchain

Real-Time Network Analytics & Monitoring

Live data from the Ninacatcoin testnet

Autorefresh is OFF

Tx hash: 08b99431a9e7ceff574c9e2664bc8bccd61133879c3d1c33f41594bd10ea513b

Tx prefix hash: dbbccee7c8982516a4f5a6fc96a213d25d02f600d2cd44b8e23a2c635c7fd8df
Tx public key: 7d4e2b2af886ee27fa388db2222c638bcb9ee4236e213a4f9d9b0f029147bf5f
Timestamp: 1773806334 Timestamp [UTC]: 2026-03-18 03:58:54 Age [y:d:h:m:s]: 00:003:07:47:55
Block: 3569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1037 RingCT/type: yes/0
Extra: 017d4e2b2af886ee27fa388db2222c638bcb9ee4236e213a4f9d9b0f029147bf5f021100000002ddbddfc9000000000000000000

1 output(s) for total of 16.578748185181 nia

stealth address amount amount idx tag
00: 8c131b88be3f86823591ca931b7f29c82cba086c0c80cbac7f618a39372ea548 16.578748185181 6150 of 0 <41>

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": 3599, "vin": [ { "gen": { "height": 3569 } } ], "vout": [ { "amount": 16578748185181, "target": { "tagged_key": { "key": "8c131b88be3f86823591ca931b7f29c82cba086c0c80cbac7f618a39372ea548", "view_tag": "41" } } } ], "extra": [ 1, 125, 78, 43, 42, 248, 134, 238, 39, 250, 56, 141, 178, 34, 44, 99, 139, 203, 158, 228, 35, 110, 33, 58, 79, 157, 155, 15, 2, 145, 71, 191, 95, 2, 17, 0, 0, 0, 2, 221, 189, 223, 201, 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