Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e627cf87931edbe492e860c5730e065c3b8e8d4ba3f03aa2c1486b97a9604b11

Tx prefix hash: f6432eac590fcde39b3e8c7c036e3cba30b5cc6cef6cffe86c2898e57429b23a
Tx public key: fd00d817e7ca702d8e616994a0b96ee16641d62662912996285442a2cc504fe9
Timestamp: 1736689495 Timestamp [UCT]: 2025-01-12 13:44:55 Age [y:d:h:m:s]: 00:084:13:32:16
Block: 1195778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60203 RingCT/type: yes/0
Extra: 01fd00d817e7ca702d8e616994a0b96ee16641d62662912996285442a2cc504fe90211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6015e6e0c7eaf779f6bca24dfc933f0d27a1f056caf7e204eac532442c03d3c5 0.600000000000 1682371 of 15

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": 1195788, "vin": [ { "gen": { "height": 1195778 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6015e6e0c7eaf779f6bca24dfc933f0d27a1f056caf7e204eac532442c03d3c5" } } ], "extra": [ 1, 253, 0, 216, 23, 231, 202, 112, 45, 142, 97, 105, 148, 160, 185, 110, 225, 102, 65, 214, 38, 98, 145, 41, 150, 40, 84, 66, 162, 204, 80, 79, 233, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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