Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a62c4159941dc6eb80c7486cb50642b713dc06847e4d015c36afeedf68e85ab5

Tx prefix hash: f5eb87b369d38f87b1582405c468d5a6c39ca917e3419a914582fd841195407e
Tx public key: 8af408265a27db8b50471cc195d5f410842e1f2b9cf6f0aa08a2afb0b6a333ae
Timestamp: 1652202207 Timestamp [UCT]: 2022-05-10 17:03:27 Age [y:d:h:m:s]: 03:174:18:41:16
Block: 498127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 903781 RingCT/type: yes/0
Extra: 018af408265a27db8b50471cc195d5f410842e1f2b9cf6f0aa08a2afb0b6a333ae0211000000065eb576c5000000000000000000

1 output(s) for total of 13.724567734000 dcy

stealth address amount amount idx
00: 7f6c7b2519f5a1aee4b57fc528ae0733b8ba87dd835e94642f76d8d0bc455dc3 13.724567734000 922294 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": 498137, "vin": [ { "gen": { "height": 498127 } } ], "vout": [ { "amount": 13724567734, "target": { "key": "7f6c7b2519f5a1aee4b57fc528ae0733b8ba87dd835e94642f76d8d0bc455dc3" } } ], "extra": [ 1, 138, 244, 8, 38, 90, 39, 219, 139, 80, 71, 28, 193, 149, 213, 244, 16, 132, 46, 31, 43, 156, 246, 240, 170, 8, 162, 175, 176, 182, 163, 51, 174, 2, 17, 0, 0, 0, 6, 94, 181, 118, 197, 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