Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 206fb788353828f9313c2d0d1bb42e2d82f4f013bf577ab5c05e9da005c240cf

Tx prefix hash: 6d267ed6d6c2431c3d0d11377e01785ce125492c54234caa24abf42bbcc9b3d2
Tx public key: a0b411d99aecfc8de64a84bd38e36f717dd360193f5cbca2a1ad5eca2d7820d8
Timestamp: 1684964138 Timestamp [UCT]: 2023-05-24 21:35:38 Age [y:d:h:m:s]: 01:240:02:22:12
Block: 767350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 432983 RingCT/type: yes/0
Extra: 01a0b411d99aecfc8de64a84bd38e36f717dd360193f5cbca2a1ad5eca2d7820d8021100000002b3164c24000000000000000000

1 output(s) for total of 1.759750453000 dcy

stealth address amount amount idx
00: 8c67340e1171fa2cc971266eeaef47eb04ebcf66e4372832e6cb70a54884e717 1.759750453000 1216467 of 0

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": 767360, "vin": [ { "gen": { "height": 767350 } } ], "vout": [ { "amount": 1759750453, "target": { "key": "8c67340e1171fa2cc971266eeaef47eb04ebcf66e4372832e6cb70a54884e717" } } ], "extra": [ 1, 160, 180, 17, 217, 154, 236, 252, 141, 230, 74, 132, 189, 56, 227, 111, 113, 125, 211, 96, 25, 63, 92, 188, 162, 161, 173, 94, 202, 45, 120, 32, 216, 2, 17, 0, 0, 0, 2, 179, 22, 76, 36, 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