🏠 Home 📊 Dashboard 💧 Mempool

Ninacatcoin Blockchain

Real-Time Network Analytics & Monitoring

Live data from the Ninacatcoin testnet

Autorefresh is OFF

Tx hash: ecd424a72a197e6e2d142e651133da08161301f0df5b27c8288fb13ca3150ed7

Tx prefix hash: 79014b9aebedf0c7cfb63ec99eb62a0d029f90a8d38cd3873d9a89537eb5f672
Tx public key: 30d1c07d9c5280d94c56eaa6bf02c7b3f1aaa4eb2a54f23b98893e4255ec260c
Timestamp: 1773650045 Timestamp [UTC]: 2026-03-16 08:34:05 Age [y:d:h:m:s]: 00:000:03:48:40
Block: 2330 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 139 RingCT/type: yes/0
Extra: 0130d1c07d9c5280d94c56eaa6bf02c7b3f1aaa4eb2a54f23b98893e4255ec260c021100000001b01731e3000000000000000000

1 output(s) for total of 16.601500501243 nia

stealth address amount amount idx tag
00: ca0f55b267c263792ba5d91b84b2ec77dbb6dc0e5bfebade1ecb5107336c132b 16.601500501243 4398 of 0 <44>

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": 2360, "vin": [ { "gen": { "height": 2330 } } ], "vout": [ { "amount": 16601500501243, "target": { "tagged_key": { "key": "ca0f55b267c263792ba5d91b84b2ec77dbb6dc0e5bfebade1ecb5107336c132b", "view_tag": "44" } } } ], "extra": [ 1, 48, 209, 192, 125, 156, 82, 128, 217, 76, 86, 234, 166, 191, 2, 199, 179, 241, 170, 164, 235, 42, 84, 242, 59, 152, 137, 62, 66, 85, 236, 38, 12, 2, 17, 0, 0, 0, 1, 176, 23, 49, 227, 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