🏠 Home 📊 Dashboard 💧 Mempool

Ninacatcoin Blockchain

Real-Time Network Analytics & Monitoring

Live data from the Ninacatcoin testnet

Autorefresh is OFF

Tx hash: 5916b8eb4ee9143999d52f384dbb00ed583b3df8c39082e4f221c4b7c032e350

Tx prefix hash: 78745430b3df9839190f5837721759030b33895d54308c4b3e6ce4ccd910e848
Tx public key: 40cdfd562fe059a1c19c6c7c7635ccdb5ca3251692a1a84e28536d4f3f9f342a
Timestamp: 1773578542 Timestamp [UTC]: 2026-03-15 12:42:22 Age [y:d:h:m:s]: 00:006:19:47:01
Block: 1745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 4323 RingCT/type: yes/0
Extra: 0140cdfd562fe059a1c19c6c7c7635ccdb5ca3251692a1a84e28536d4f3f9f342a0211000000020498e89f000000000000000000

1 output(s) for total of 16.614170017783 nia

stealth address amount amount idx tag
00: 07343b4063935b1e3d84f7518d74baf933554ce537014f91c1ffd30e5d8b81f6 16.614170017783 3094 of 0 <98>

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": 1775, "vin": [ { "gen": { "height": 1745 } } ], "vout": [ { "amount": 16614170017783, "target": { "tagged_key": { "key": "07343b4063935b1e3d84f7518d74baf933554ce537014f91c1ffd30e5d8b81f6", "view_tag": "98" } } } ], "extra": [ 1, 64, 205, 253, 86, 47, 224, 89, 161, 193, 156, 108, 124, 118, 53, 204, 219, 92, 163, 37, 22, 146, 161, 168, 78, 40, 83, 109, 79, 63, 159, 52, 42, 2, 17, 0, 0, 0, 2, 4, 152, 232, 159, 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