Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20017c986809c2d140994d2a5a3acedd0ba9523db7c5e487afe7654f9a134ffe

Tx prefix hash: bcf05c5bff0e02a30ee220300ab2f185f0371daeb977af7f5a4bbe6770c7632a
Tx public key: 3ff396ccd5d4dc8df817b38e943374d5689290c7df50969f1c3a3a6535f6fc2c
Timestamp: 1736410782 Timestamp [UCT]: 2025-01-09 08:19:42 Age [y:d:h:m:s]: 00:070:10:59:17
Block: 1193468 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50151 RingCT/type: yes/0
Extra: 013ff396ccd5d4dc8df817b38e943374d5689290c7df50969f1c3a3a6535f6fc2c0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 866e35646bf12b97ef300fbae203c65f9dd4f008076d83d51cd20366e86e4849 0.600000000000 1680029 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": 1193478, "vin": [ { "gen": { "height": 1193468 } } ], "vout": [ { "amount": 600000000, "target": { "key": "866e35646bf12b97ef300fbae203c65f9dd4f008076d83d51cd20366e86e4849" } } ], "extra": [ 1, 63, 243, 150, 204, 213, 212, 220, 141, 248, 23, 179, 142, 148, 51, 116, 213, 104, 146, 144, 199, 223, 80, 150, 159, 28, 58, 58, 101, 53, 246, 252, 44, 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