🏠 Home 📊 Dashboard 💧 Mempool

Ninacatcoin Blockchain

Real-Time Network Analytics & Monitoring

Live data from the Ninacatcoin testnet

Autorefresh is OFF

Tx hash: 2a6ae66cb172c54c146045b6356d5ae037d00f4db48bfd13185aa86a3daa909f

Tx prefix hash: ced35b22bb8375b2e7300b57969ed5d8a43c45fc7d8de8eb0766c0aceb983305
Tx public key: 3c427b287215b03f6d0000f4fc7cf9ebe7a0ab333193d236289ff34be7836779
Timestamp: 1773582156 Timestamp [UTC]: 2026-03-15 13:42:36 Age [y:d:h:m:s]: 00:000:22:27:32
Block: 1775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 690 RingCT/type: yes/0
Extra: 013c427b287215b03f6d0000f4fc7cf9ebe7a0ab333193d236289ff34be78367790211000000020ae69111000000000000000000

1 output(s) for total of 16.613262843865 nia

stealth address amount amount idx tag
00: 4c780a196f93d24161453b4e5e56d1acc9c6cd9639ed5eba6c9d1aa31ef1b6b7 16.613262843865 3156 of 0 <e4>

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": 1805, "vin": [ { "gen": { "height": 1775 } } ], "vout": [ { "amount": 16613262843865, "target": { "tagged_key": { "key": "4c780a196f93d24161453b4e5e56d1acc9c6cd9639ed5eba6c9d1aa31ef1b6b7", "view_tag": "e4" } } } ], "extra": [ 1, 60, 66, 123, 40, 114, 21, 176, 63, 109, 0, 0, 244, 252, 124, 249, 235, 231, 160, 171, 51, 49, 147, 210, 54, 40, 159, 243, 75, 231, 131, 103, 121, 2, 17, 0, 0, 0, 2, 10, 230, 145, 17, 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