Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8aa6621b59193def7e869fda33fac3ba1aa9de7107a87cd614b791917d17857

Tx prefix hash: 052235a2cf8ccb7c0ae3264450fbf99620ef13523c9d5587d3ab6436641b6354
Tx public key: bcd51b4b727a858313d53c7568e5bac6eb8ebd6b190ae020921707432548d615
Timestamp: 1650634559 Timestamp [UCT]: 2022-04-22 13:35:59 Age [y:d:h:m:s]: 02:248:04:13:14
Block: 485697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 697338 RingCT/type: yes/0
Extra: 01bcd51b4b727a858313d53c7568e5bac6eb8ebd6b190ae020921707432548d615021100000001cb8520c2000000000000000000

1 output(s) for total of 15.089833334000 dcy

stealth address amount amount idx
00: af27b59b1287a2a8e5c23f7602dbe34080c1c8f1f4fff2669f838780a7a72a67 15.089833334000 907824 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": 485707, "vin": [ { "gen": { "height": 485697 } } ], "vout": [ { "amount": 15089833334, "target": { "key": "af27b59b1287a2a8e5c23f7602dbe34080c1c8f1f4fff2669f838780a7a72a67" } } ], "extra": [ 1, 188, 213, 27, 75, 114, 122, 133, 131, 19, 213, 60, 117, 104, 229, 186, 198, 235, 142, 189, 107, 25, 10, 224, 32, 146, 23, 7, 67, 37, 72, 214, 21, 2, 17, 0, 0, 0, 1, 203, 133, 32, 194, 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