Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6299628d1e0026537cf7cc5ec7fed7d54c21a04e504902494bca9ed848a1bc12

Tx prefix hash: b6fc819346d14f96446de66dbf1053f3a64206d9cedf6a986c4edd714adc31c3
Tx public key: 1035abe9a457701da959e2e8fa91f48d244e84b49e0d0d473618ad21f238ccf9
Timestamp: 1696589339 Timestamp [UCT]: 2023-10-06 10:48:59 Age [y:d:h:m:s]: 01:097:16:00:11
Block: 863668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331062 RingCT/type: yes/0
Extra: 011035abe9a457701da959e2e8fa91f48d244e84b49e0d0d473618ad21f238ccf902110000000bfaf35c9c000000000000000000

1 output(s) for total of 0.843935833000 dcy

stealth address amount amount idx
00: d2be4674cb1dfac66cbca9dae86abbe950e0db71d97d13f4aaae5bebc1383b9b 0.843935833000 1318142 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": 863678, "vin": [ { "gen": { "height": 863668 } } ], "vout": [ { "amount": 843935833, "target": { "key": "d2be4674cb1dfac66cbca9dae86abbe950e0db71d97d13f4aaae5bebc1383b9b" } } ], "extra": [ 1, 16, 53, 171, 233, 164, 87, 112, 29, 169, 89, 226, 232, 250, 145, 244, 141, 36, 78, 132, 180, 158, 13, 13, 71, 54, 24, 173, 33, 242, 56, 204, 249, 2, 17, 0, 0, 0, 11, 250, 243, 92, 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