Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39b854331221c4f75d4ea1fc755e8efed6995b6e6acd7d720ae529f7918a49c4

Tx prefix hash: 9d60ba04ce3723cc8b9920af109a24b9a9061e4acc451b4de0558244bfe89809
Tx public key: 7b16daa397c764637c89b92d8b87f8c3a2c7521e8e3f572170df6806ee4bc5de
Timestamp: 1703030870 Timestamp [UCT]: 2023-12-20 00:07:50 Age [y:d:h:m:s]: 02:003:08:07:45
Block: 916882 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 522139 RingCT/type: yes/0
Extra: 017b16daa397c764637c89b92d8b87f8c3a2c7521e8e3f572170df6806ee4bc5de02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7664b17c6f20105e27c59677076be7c76d669d85d2241e246a9386c858c97b15 0.600000000000 1374444 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": 916892, "vin": [ { "gen": { "height": 916882 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7664b17c6f20105e27c59677076be7c76d669d85d2241e246a9386c858c97b15" } } ], "extra": [ 1, 123, 22, 218, 163, 151, 199, 100, 99, 124, 137, 185, 45, 139, 135, 248, 195, 162, 199, 82, 30, 142, 63, 87, 33, 112, 223, 104, 6, 238, 75, 197, 222, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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