Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 053c6a1364184dfddc96e10c8e6cb65d392719aebe9d3f1cbcb639cb67009c34

Tx prefix hash: c2297d8eedb6584fc0d68325eb7bfbfde161ec027532bb8623cfcb433e8f4467
Tx public key: 9b2637a60d1cb5e0d60c004443b7e542ce564b08d9e77c01778af8a9193a65ab
Timestamp: 1603726545 Timestamp [UCT]: 2020-10-26 15:35:45 Age [y:d:h:m:s]: 04:061:00:15:03
Block: 144133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1038838 RingCT/type: yes/0
Extra: 019b2637a60d1cb5e0d60c004443b7e542ce564b08d9e77c01778af8a9193a65ab0211000000078b34f601000000000000000000

1 output(s) for total of 204.375220164000 dcy

stealth address amount amount idx
00: 3892455026016c08b9b32f011de1d91b5a6a01597a35cc9e6b96182f7f3a5396 204.375220164000 239589 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": 144143, "vin": [ { "gen": { "height": 144133 } } ], "vout": [ { "amount": 204375220164, "target": { "key": "3892455026016c08b9b32f011de1d91b5a6a01597a35cc9e6b96182f7f3a5396" } } ], "extra": [ 1, 155, 38, 55, 166, 13, 28, 181, 224, 214, 12, 0, 68, 67, 183, 229, 66, 206, 86, 75, 8, 217, 231, 124, 1, 119, 138, 248, 169, 25, 58, 101, 171, 2, 17, 0, 0, 0, 7, 139, 52, 246, 1, 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