Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae6724640ea6f83fcaa915cbe86a3213d28e9181b134d2e6f7a20424af711479

Tx prefix hash: e520025c93dafb828aaa969466fa3e52b9e2fd17a6da2ad21a3209237e429e06
Tx public key: 9e63537189862a033922fdde33e4ea55befb7a4c50f93aef5d0ab84d8e41d02b
Timestamp: 1728309376 Timestamp [UCT]: 2024-10-07 13:56:16 Age [y:d:h:m:s]: 00:110:16:15:43
Block: 1126448 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79072 RingCT/type: yes/0
Extra: 019e63537189862a033922fdde33e4ea55befb7a4c50f93aef5d0ab84d8e41d02b02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72788bda9c931a5daf130bca6a00c56896b54aca6a5b6693ab397270eacc749c 0.600000000000 1609241 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": 1126458, "vin": [ { "gen": { "height": 1126448 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72788bda9c931a5daf130bca6a00c56896b54aca6a5b6693ab397270eacc749c" } } ], "extra": [ 1, 158, 99, 83, 113, 137, 134, 42, 3, 57, 34, 253, 222, 51, 228, 234, 85, 190, 251, 122, 76, 80, 249, 58, 239, 93, 10, 184, 77, 142, 65, 208, 43, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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