Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ad6898c558e51c00a06b9290c1e5b21b22ccfde14a8426af5fdec34f3e317a7

Tx prefix hash: eb588126ba32e1214c5b982f28f03e64fe64a1062425e412175f221e13ec3d7b
Tx public key: 59fe6dcebb54dee4f8353b634e6efa4e3e4eeb8bf72c421d412a85114aabc87f
Timestamp: 1760347883 Timestamp [UCT]: 2025-10-13 09:31:23 Age [y:d:h:m:s]: 00:024:16:12:06
Block: 1388941 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17661 RingCT/type: yes/0
Extra: 0159fe6dcebb54dee4f8353b634e6efa4e3e4eeb8bf72c421d412a85114aabc87f021100000001df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df3bc1954fdaa86cd93b09b74fd0b6078024aa21fee6e66005b105a801324a1e 0.600000000000 1877164 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": 1388951, "vin": [ { "gen": { "height": 1388941 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df3bc1954fdaa86cd93b09b74fd0b6078024aa21fee6e66005b105a801324a1e" } } ], "extra": [ 1, 89, 254, 109, 206, 187, 84, 222, 228, 248, 53, 59, 99, 78, 110, 250, 78, 62, 78, 235, 139, 247, 44, 66, 29, 65, 42, 133, 17, 74, 171, 200, 127, 2, 17, 0, 0, 0, 1, 223, 90, 36, 122, 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