Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f809e7d276537a9d315a05b7c80043db200415269cf6f3274e1c5497ffe3b7fc

Tx prefix hash: 3578058e5e5ef0509c41782a09eb08419e20be50f1abc5a9f9351208f669b78f
Tx public key: dffd8c4619e7ba68b17ea4f897f319f6519eddc9ef0ffd0554a9699b074137c7
Timestamp: 1736029193 Timestamp [UCT]: 2025-01-04 22:19:53 Age [y:d:h:m:s]: 00:093:17:07:46
Block: 1190317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66757 RingCT/type: yes/0
Extra: 01dffd8c4619e7ba68b17ea4f897f319f6519eddc9ef0ffd0554a9699b074137c70211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7817c9bfabf3ba37271536851cc0899d4c3ddc279870f7fe003eb05c45db2c3c 0.600000000000 1676832 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": 1190327, "vin": [ { "gen": { "height": 1190317 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7817c9bfabf3ba37271536851cc0899d4c3ddc279870f7fe003eb05c45db2c3c" } } ], "extra": [ 1, 223, 253, 140, 70, 25, 231, 186, 104, 177, 126, 164, 248, 151, 243, 25, 246, 81, 158, 221, 201, 239, 15, 253, 5, 84, 169, 105, 155, 7, 65, 55, 199, 2, 17, 0, 0, 0, 3, 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