Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: ed542dfbfdbab56e3eb89fdad3aa7bd4cbe3b5e92aad00960aaa8078dd2bd1ed

Tx prefix hash: 6c0dc819267208bf1cf1c7b278d79519cacdc371489231b703d3b17f97b46d76
Tx public key: 6ac65f8a7b4cced5e24e9b71c8917223739fc2ce296d9ac96f28b02ee2aa9c4c
Timestamp: 1735335149 Timestamp [UCT]: 2024-12-27 21:32:29 Age [y:d:h:m:s]: 00:085:00:07:00
Block: 1184558 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60550 RingCT/type: yes/0
Extra: 016ac65f8a7b4cced5e24e9b71c8917223739fc2ce296d9ac96f28b02ee2aa9c4c0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 09d35e17aac819ba510f8042616dc3508c1556a64a7fe9201bececbd60b3fd9a 0.600000000000 1671015 of 15

Check which outputs belong to given Dinastycoin 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 Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-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": 1184568, "vin": [ { "gen": { "height": 1184558 } } ], "vout": [ { "amount": 600000000, "target": { "key": "09d35e17aac819ba510f8042616dc3508c1556a64a7fe9201bececbd60b3fd9a" } } ], "extra": [ 1, 106, 198, 95, 138, 123, 76, 206, 213, 226, 78, 155, 113, 200, 145, 114, 35, 115, 159, 194, 206, 41, 109, 154, 201, 111, 40, 176, 46, 226, 170, 156, 76, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8