Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5f782c3140cf465e48f51a99698cf37fe70fa06aebfd3d003f4f664c7fdb2ba

Tx prefix hash: 81eeefeb7eb350825aac950efe850f34dbb7f4b7952618177a08aed2e075d4b5
Tx public key: d36ea2f88b8f3bd0f2de64263ad0e267dbac7f4bf4ca9164159cbf0163cd33e1
Timestamp: 1720595624 Timestamp [UCT]: 2024-07-10 07:13:44 Age [y:d:h:m:s]: 00:228:04:09:46
Block: 1062502 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162961 RingCT/type: yes/0
Extra: 01d36ea2f88b8f3bd0f2de64263ad0e267dbac7f4bf4ca9164159cbf0163cd33e102110000000f91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8bd6e9517aff2827724d398f6eaa5efcab3ced4653f0725f8c61a835188952dc 0.600000000000 1533005 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": 1062512, "vin": [ { "gen": { "height": 1062502 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8bd6e9517aff2827724d398f6eaa5efcab3ced4653f0725f8c61a835188952dc" } } ], "extra": [ 1, 211, 110, 162, 248, 139, 143, 59, 208, 242, 222, 100, 38, 58, 208, 226, 103, 219, 172, 127, 75, 244, 202, 145, 100, 21, 156, 191, 1, 99, 205, 51, 225, 2, 17, 0, 0, 0, 15, 145, 225, 60, 4, 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