Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa203ec00ec12ef5127a7e1728e7791324a9a971c93eafaaf13669c1ef94ccb2

Tx prefix hash: 377fb6a22c6859a578b7a86dd89098b95ca11b6699468cbe26265599bd53c193
Tx public key: 57b7f66bf62ba26a2b969217b1d0ca7ef950e6d47463e93bef6c24d618c5fe54
Timestamp: 1577194068 Timestamp [UCT]: 2019-12-24 13:27:48 Age [y:d:h:m:s]: 05:005:14:21:08
Block: 30734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1154010 RingCT/type: yes/0
Extra: 0157b7f66bf62ba26a2b969217b1d0ca7ef950e6d47463e93bef6c24d618c5fe540211000000134ac5aa02000000000000000000

1 output(s) for total of 485.474430468000 dcy

stealth address amount amount idx
00: 2f14d5c570ca141988724dbc485555086c830a98f0244bfd93d7b30bc18836df 485.474430468000 50740 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": 30744, "vin": [ { "gen": { "height": 30734 } } ], "vout": [ { "amount": 485474430468, "target": { "key": "2f14d5c570ca141988724dbc485555086c830a98f0244bfd93d7b30bc18836df" } } ], "extra": [ 1, 87, 183, 246, 107, 246, 43, 162, 106, 43, 150, 146, 23, 177, 208, 202, 126, 249, 80, 230, 212, 116, 99, 233, 59, 239, 108, 36, 214, 24, 197, 254, 84, 2, 17, 0, 0, 0, 19, 74, 197, 170, 2, 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