Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72eda7e56a9ef504d49b207394c410f0e9c774f6dd770ea34e7d795f191fd951

Tx prefix hash: 1aace9d5b3898d80eadbde241e8d77379cf46473de4d6f3e6a1f37a46454cddd
Tx public key: 500ba7b5b18413dcfbf9abcd13e5260dba214e77d3799e993533eb5d182f4cf3
Timestamp: 1736416886 Timestamp [UCT]: 2025-01-09 10:01:26 Age [y:d:h:m:s]: 00:290:11:03:03
Block: 1193515 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205088 RingCT/type: yes/0
Extra: 01500ba7b5b18413dcfbf9abcd13e5260dba214e77d3799e993533eb5d182f4cf30211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b644390ab20b11ecdf9a6c311021945e483c0d0be28f815fd430220dbf867a2e 0.600000000000 1680076 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": 1193525, "vin": [ { "gen": { "height": 1193515 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b644390ab20b11ecdf9a6c311021945e483c0d0be28f815fd430220dbf867a2e" } } ], "extra": [ 1, 80, 11, 167, 181, 177, 132, 19, 220, 251, 249, 171, 205, 19, 229, 38, 13, 186, 33, 78, 119, 211, 121, 158, 153, 53, 51, 235, 93, 24, 47, 76, 243, 2, 17, 0, 0, 0, 7, 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