Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6dd1dbc0d62e5c78cb9cac82bba879e990bc7db01fb158352a8247f1e78f322b

Tx prefix hash: 324e9a2424f978cd16964003af457f562aea4a9b5896b02ee14d40613559e585
Tx public key: a08574790f83f5def10aa5f0543fb46036d8d5c0ca8dccecc44ad52a841eaf48
Timestamp: 1697026347 Timestamp [UCT]: 2023-10-11 12:12:27 Age [y:d:h:m:s]: 01:102:19:10:19
Block: 867299 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334684 RingCT/type: yes/0
Extra: 01a08574790f83f5def10aa5f0543fb46036d8d5c0ca8dccecc44ad52a841eaf4802110000000a4b8f5122000000000000000000

1 output(s) for total of 0.820877612000 dcy

stealth address amount amount idx
00: a486ad86ba49bf0a9ebb874d52ec7a86cf16103313894786c6262116f47f01f0 0.820877612000 1321973 of 0

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": 867309, "vin": [ { "gen": { "height": 867299 } } ], "vout": [ { "amount": 820877612, "target": { "key": "a486ad86ba49bf0a9ebb874d52ec7a86cf16103313894786c6262116f47f01f0" } } ], "extra": [ 1, 160, 133, 116, 121, 15, 131, 245, 222, 241, 10, 165, 240, 84, 63, 180, 96, 54, 216, 213, 192, 202, 141, 204, 236, 196, 74, 213, 42, 132, 30, 175, 72, 2, 17, 0, 0, 0, 10, 75, 143, 81, 34, 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