Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a5bda11833438358e8d46a201cc065ba20f8c16d78ffcd55317b71e513d15d9

Tx prefix hash: fd289b2eab3bc4f15a1f43c5dc948b3b727595c0d476013d7cdf893290417408
Tx public key: 52fe44a539ef0aec3d0ff618ff7da13e68d0e8c325eb6f133c264522deafd8ca
Timestamp: 1711100925 Timestamp [UCT]: 2024-03-22 09:48:45 Age [y:d:h:m:s]: 01:040:07:29:54
Block: 983799 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289780 RingCT/type: yes/0
Extra: 0152fe44a539ef0aec3d0ff618ff7da13e68d0e8c325eb6f133c264522deafd8ca0211000000010424019c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f1ac896a563572099a41e0e51df8ce301dd6aab61713a6c345988907b33ac6d 0.600000000000 1443946 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": 983809, "vin": [ { "gen": { "height": 983799 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f1ac896a563572099a41e0e51df8ce301dd6aab61713a6c345988907b33ac6d" } } ], "extra": [ 1, 82, 254, 68, 165, 57, 239, 10, 236, 61, 15, 246, 24, 255, 125, 161, 62, 104, 208, 232, 195, 37, 235, 111, 19, 60, 38, 69, 34, 222, 175, 216, 202, 2, 17, 0, 0, 0, 1, 4, 36, 1, 156, 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