Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65f592072f0ff1fa901f9f8ff4cda5b8ba773736c2ce1c8d7c658e5a91e62b4e

Tx prefix hash: e56ce1b5cc83a6083551327618cecbbe64d963779d7ad33be5febaf878cb6ce4
Tx public key: 111062ed8fa02e8d6c5299d2be4cf09f3c86ca5e511557be539e0844ae6bc133
Timestamp: 1702316885 Timestamp [UCT]: 2023-12-11 17:48:05 Age [y:d:h:m:s]: 01:324:08:33:04
Block: 910956 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 490669 RingCT/type: yes/0
Extra: 01111062ed8fa02e8d6c5299d2be4cf09f3c86ca5e511557be539e0844ae6bc133021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c864efe162fdbb8f1392b0c303dcf4973a02852ed9e114908c89c27502861f52 0.600000000000 1368131 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": 910966, "vin": [ { "gen": { "height": 910956 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c864efe162fdbb8f1392b0c303dcf4973a02852ed9e114908c89c27502861f52" } } ], "extra": [ 1, 17, 16, 98, 237, 143, 160, 46, 141, 108, 82, 153, 210, 190, 76, 240, 159, 60, 134, 202, 94, 81, 21, 87, 190, 83, 158, 8, 68, 174, 107, 193, 51, 2, 17, 0, 0, 0, 7, 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