Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6896452d867377e7659b23664fd8fd878cb6f1e2bbfc746aa247ac93ce53bed

Tx prefix hash: c6e0a1c74af2cbcc7c9224cd086fbc13806ec72dbeaf3b73604d9f42ab7b8542
Tx public key: f73ff7535fe9793f79fafe3a9fd05c71151ab5eb9ae07fd2a4d851caff9a8546
Timestamp: 1733695072 Timestamp [UCT]: 2024-12-08 21:57:52 Age [y:d:h:m:s]: 00:107:12:25:53
Block: 1171011 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76600 RingCT/type: yes/0
Extra: 01f73ff7535fe9793f79fafe3a9fd05c71151ab5eb9ae07fd2a4d851caff9a8546021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a69275d3a4c08ecfb6e71222924b2e056c5d0531e65eddaeb05e4485a94173e2 0.600000000000 1656746 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": 1171021, "vin": [ { "gen": { "height": 1171011 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a69275d3a4c08ecfb6e71222924b2e056c5d0531e65eddaeb05e4485a94173e2" } } ], "extra": [ 1, 247, 63, 247, 83, 95, 233, 121, 63, 121, 250, 254, 58, 159, 208, 92, 113, 21, 26, 181, 235, 154, 224, 127, 210, 164, 216, 81, 202, 255, 154, 133, 70, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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