Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cded2b2b5507097738b323635ffc135b2bcc64bc22464af2ad03da3a25916c14

Tx prefix hash: f7a463d5b1e0365f4e591d74584ccb26fb840d7a85427576052e18e2a48c0329
Tx public key: f1de592c6be5cb842c8e2c7337db05e5aa130d1642c821dd3df83b7d5b97bece
Timestamp: 1765088373 Timestamp [UCT]: 2025-12-07 06:19:33 Age [y:d:h:m:s]: 00:016:15:45:02
Block: 1428231 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11913 RingCT/type: yes/0
Extra: 01f1de592c6be5cb842c8e2c7337db05e5aa130d1642c821dd3df83b7d5b97bece0211000000017b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4447bb8fc89e285fc0a4ce3b1fa7f7712bbe2f21533583d8af3419793384f061 0.600000000000 1916944 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": 1428241, "vin": [ { "gen": { "height": 1428231 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4447bb8fc89e285fc0a4ce3b1fa7f7712bbe2f21533583d8af3419793384f061" } } ], "extra": [ 1, 241, 222, 89, 44, 107, 229, 203, 132, 44, 142, 44, 115, 55, 219, 5, 229, 170, 19, 13, 22, 66, 200, 33, 221, 61, 248, 59, 125, 91, 151, 190, 206, 2, 17, 0, 0, 0, 1, 123, 30, 81, 172, 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