Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ee4a1a1d54e95d1faa82c9b2911381b336433e5fd0c228d88f179d336f1532d

Tx prefix hash: bcbc73de6eaed6829720830690a35d70e3de7b847119e24e3abad62589ead535
Tx public key: ecd60c30ef1ee19d02ae78e76a93ad5736a0c78759c5d65e6c05737b7f90be9e
Timestamp: 1703776589 Timestamp [UCT]: 2023-12-28 15:16:29 Age [y:d:h:m:s]: 01:082:15:01:19
Block: 923049 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320185 RingCT/type: yes/0
Extra: 01ecd60c30ef1ee19d02ae78e76a93ad5736a0c78759c5d65e6c05737b7f90be9e021100000002ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33c1d0ff7fdf4b672dfbcaa2e044feaedb55a359ee2db7196cb7ad449ed13e64 0.600000000000 1380765 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": 923059, "vin": [ { "gen": { "height": 923049 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33c1d0ff7fdf4b672dfbcaa2e044feaedb55a359ee2db7196cb7ad449ed13e64" } } ], "extra": [ 1, 236, 214, 12, 48, 239, 30, 225, 157, 2, 174, 120, 231, 106, 147, 173, 87, 54, 160, 199, 135, 89, 197, 214, 94, 108, 5, 115, 123, 127, 144, 190, 158, 2, 17, 0, 0, 0, 2, 173, 86, 148, 172, 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