Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 789f78a868916c959327fff470271772b95286a9d929100f6e6ab16b3fc3a9d2

Tx prefix hash: 3cc6dfe9196e9ba9856599f6d3546a82e82f069b84563973d66a75bb7cc4b876
Tx public key: 7de9fbfb45d3154c7be501b03fdee4a05e8adf05925ea0def455a387cf95a2c6
Timestamp: 1577197071 Timestamp [UCT]: 2019-12-24 14:17:51 Age [y:d:h:m:s]: 05:071:00:02:20
Block: 30773 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1200516 RingCT/type: yes/0
Extra: 017de9fbfb45d3154c7be501b03fdee4a05e8adf05925ea0def455a387cf95a2c6021100000059398c17aa000000000000000000

1 output(s) for total of 485.330000243000 dcy

stealth address amount amount idx
00: 5c5556907600dca62535ec6eeb9925241aa5554d75d56ba06eb3673adf989ee8 485.330000243000 50803 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": 30783, "vin": [ { "gen": { "height": 30773 } } ], "vout": [ { "amount": 485330000243, "target": { "key": "5c5556907600dca62535ec6eeb9925241aa5554d75d56ba06eb3673adf989ee8" } } ], "extra": [ 1, 125, 233, 251, 251, 69, 211, 21, 76, 123, 229, 1, 176, 63, 222, 228, 160, 94, 138, 223, 5, 146, 94, 160, 222, 244, 85, 163, 135, 207, 149, 162, 198, 2, 17, 0, 0, 0, 89, 57, 140, 23, 170, 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