Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62a3368e2a675a767967bf84fc56a5523c6fda307aff908320aeb9a92efde02e

Tx prefix hash: 960cb2788e9bbcb5c834cbdf9724a998b70a160d19d04afaa87a974c2d78d08c
Tx public key: 7ad6fba798d2c2e5be60c96d9b19f510be3fc3360dba33c7847966f41a12c930
Timestamp: 1703486115 Timestamp [UCT]: 2023-12-25 06:35:15 Age [y:d:h:m:s]: 01:114:23:28:57
Block: 920648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 343303 RingCT/type: yes/0
Extra: 017ad6fba798d2c2e5be60c96d9b19f510be3fc3360dba33c7847966f41a12c9300211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ccec7b984fb584c5dbf4860742e5acf913048fb4c67dfe0f3d261ef2919e7c9 0.600000000000 1378328 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": 920658, "vin": [ { "gen": { "height": 920648 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ccec7b984fb584c5dbf4860742e5acf913048fb4c67dfe0f3d261ef2919e7c9" } } ], "extra": [ 1, 122, 214, 251, 167, 152, 210, 194, 229, 190, 96, 201, 109, 155, 25, 245, 16, 190, 63, 195, 54, 13, 186, 51, 199, 132, 121, 102, 244, 26, 18, 201, 48, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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