Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42bba7bd18057a346d3be679c563a139d11ee7c01f72c829227dd869d22aac6f

Tx prefix hash: 8abc24cb11b20e902d30dfa2cbe51c23f3934b486c34c2c93c4e61945e6356ec
Tx public key: 757a512fe63370d5b5da8eb6a8e33c6b209fb63175b744b83be56099826f7160
Timestamp: 1696928424 Timestamp [UCT]: 2023-10-10 09:00:24 Age [y:d:h:m:s]: 01:198:03:41:34
Block: 866496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 402658 RingCT/type: yes/0
Extra: 01757a512fe63370d5b5da8eb6a8e33c6b209fb63175b744b83be56099826f7160021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.825922096000 dcy

stealth address amount amount idx
00: e9746ae45034ba071536393be742aecd3c5a6852df78762f02085cb694109816 0.825922096000 1321092 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": 866506, "vin": [ { "gen": { "height": 866496 } } ], "vout": [ { "amount": 825922096, "target": { "key": "e9746ae45034ba071536393be742aecd3c5a6852df78762f02085cb694109816" } } ], "extra": [ 1, 117, 122, 81, 47, 230, 51, 112, 213, 181, 218, 142, 182, 168, 227, 60, 107, 32, 159, 182, 49, 117, 183, 68, 184, 59, 229, 96, 153, 130, 111, 113, 96, 2, 17, 0, 0, 0, 4, 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