Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 729ac0708daa2fb1be4320de99c0a641fa8c5c2068ff4f1b804002a8124cfed5

Tx prefix hash: 28ef26d85178540bd0216ffa189f3f8da5feebef6a5812f972723a17d795f127
Tx public key: 34c703925df1d05b395e3a3219d9bf6df4d8b7f26fca2407586483a2ccd5a2f4
Timestamp: 1675676079 Timestamp [UCT]: 2023-02-06 09:34:39 Age [y:d:h:m:s]: 02:021:23:09:51
Block: 690969 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 537283 RingCT/type: yes/0
Extra: 0134c703925df1d05b395e3a3219d9bf6df4d8b7f26fca2407586483a2ccd5a2f402110000000533af99f4000000000000000000

1 output(s) for total of 3.151612357000 dcy

stealth address amount amount idx
00: ae22464636865fcc6203e665d3e0542540599746c643a55fce0ced205d140274 3.151612357000 1133711 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": 690979, "vin": [ { "gen": { "height": 690969 } } ], "vout": [ { "amount": 3151612357, "target": { "key": "ae22464636865fcc6203e665d3e0542540599746c643a55fce0ced205d140274" } } ], "extra": [ 1, 52, 199, 3, 146, 93, 241, 208, 91, 57, 94, 58, 50, 25, 217, 191, 109, 244, 216, 183, 242, 111, 202, 36, 7, 88, 100, 131, 162, 204, 213, 162, 244, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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