Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d620ed623882d56b9a50f89e13423a2678b55d506e7210652caac54695570895

Tx prefix hash: e7ef6e090017da6247a01e2b81c4c01121f397ca15499029c508c18a5a5297ab
Tx public key: 39c32d5c3826c4c27f7c4919cd86cbc6b22b2991349a7f6ab483642d6f7c7fa0
Timestamp: 1702256516 Timestamp [UCT]: 2023-12-11 01:01:56 Age [y:d:h:m:s]: 01:045:23:55:50
Block: 910454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294206 RingCT/type: yes/0
Extra: 0139c32d5c3826c4c27f7c4919cd86cbc6b22b2991349a7f6ab483642d6f7c7fa00211000000014b8f5122000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f28be4e5b343b53cfe4c8de983b94ea300146225d751e475fe58ceb6d3b35cb 0.600000000000 1367611 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": 910464, "vin": [ { "gen": { "height": 910454 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f28be4e5b343b53cfe4c8de983b94ea300146225d751e475fe58ceb6d3b35cb" } } ], "extra": [ 1, 57, 195, 45, 92, 56, 38, 196, 194, 127, 124, 73, 25, 205, 134, 203, 198, 178, 43, 41, 145, 52, 154, 127, 106, 180, 131, 100, 45, 111, 124, 127, 160, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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