Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac35733eb79cecc050b819caa466b28ee6a7d3289871b1be0ed083c3efbee6a1

Tx prefix hash: 75f75241ac31c79209494ebccd7c2436495f95dbebe28228f834e008e2210d00
Tx public key: d93582e6682d9839cc0803906efa012bdf51568e48bcf4ea0bff9a862bd786f0
Timestamp: 1697006676 Timestamp [UCT]: 2023-10-11 06:44:36 Age [y:d:h:m:s]: 01:094:07:10:06
Block: 867131 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328655 RingCT/type: yes/0
Extra: 01d93582e6682d9839cc0803906efa012bdf51568e48bcf4ea0bff9a862bd786f0021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.821930441000 dcy

stealth address amount amount idx
00: 0f6abaf41c52a9665a562c1f3cbe33ad822abee3ab20f236c50778f6e370ddb6 0.821930441000 1321787 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": 867141, "vin": [ { "gen": { "height": 867131 } } ], "vout": [ { "amount": 821930441, "target": { "key": "0f6abaf41c52a9665a562c1f3cbe33ad822abee3ab20f236c50778f6e370ddb6" } } ], "extra": [ 1, 217, 53, 130, 230, 104, 45, 152, 57, 204, 8, 3, 144, 110, 250, 1, 43, 223, 81, 86, 142, 72, 188, 244, 234, 11, 255, 154, 134, 43, 215, 134, 240, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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