Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03223de1ca35cc76f9fa33e485b95076158f54b21bb1a2007355b170b884786a

Tx prefix hash: 58790ec3810ee982f4fa470f09cd54259f59dc01ce49c5aef6467d1334b8e300
Tx public key: 25a0b60c6442fdf622f927c4de59f22ac78739f7c6825a882922b6c60e49afe8
Timestamp: 1579299604 Timestamp [UCT]: 2020-01-17 22:20:04 Age [y:d:h:m:s]: 05:053:16:43:28
Block: 47857 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1188479 RingCT/type: yes/0
Extra: 0125a0b60c6442fdf622f927c4de59f22ac78739f7c6825a882922b6c60e49afe802110000005c4943cd9f000000000000000000

1 output(s) for total of 426.020726588000 dcy

stealth address amount amount idx
00: 60b3b22ffe433345481d182710c7c4bce9e70082d0b9f4d2936d528e3c959c16 426.020726588000 88418 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": 47867, "vin": [ { "gen": { "height": 47857 } } ], "vout": [ { "amount": 426020726588, "target": { "key": "60b3b22ffe433345481d182710c7c4bce9e70082d0b9f4d2936d528e3c959c16" } } ], "extra": [ 1, 37, 160, 182, 12, 100, 66, 253, 246, 34, 249, 39, 196, 222, 89, 242, 42, 199, 135, 57, 247, 198, 130, 90, 136, 41, 34, 182, 198, 14, 73, 175, 232, 2, 17, 0, 0, 0, 92, 73, 67, 205, 159, 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