Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e6966ddd79977846cf2173a51b4ffca9e1e1aa1d3a6d3cb0c676752ae86ed99

Tx prefix hash: 2ca9dae16f55e1001913b3cacfa65dab05bc62b0c3d0c4d3602b478bade19a17
Tx public key: fe056daa1bbbb5c197ead1c7e80b26adfa4e6739b187e517a77c91a013295fcc
Timestamp: 1582555826 Timestamp [UCT]: 2020-02-24 14:50:26 Age [y:d:h:m:s]: 05:252:07:27:26
Block: 71649 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1331281 RingCT/type: yes/0
Extra: 01fe056daa1bbbb5c197ead1c7e80b26adfa4e6739b187e517a77c91a013295fcc0211000000064ac5aa02000000000000000000

1 output(s) for total of 355.302220238000 dcy

stealth address amount amount idx
00: 6457bee303e21d44626ca11ecae7b99a95cb9e3a8c2b82afeab2b2dac2d97fec 355.302220238000 132360 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": 71659, "vin": [ { "gen": { "height": 71649 } } ], "vout": [ { "amount": 355302220238, "target": { "key": "6457bee303e21d44626ca11ecae7b99a95cb9e3a8c2b82afeab2b2dac2d97fec" } } ], "extra": [ 1, 254, 5, 109, 170, 27, 187, 181, 193, 151, 234, 209, 199, 232, 11, 38, 173, 250, 78, 103, 57, 177, 135, 229, 23, 167, 124, 145, 160, 19, 41, 95, 204, 2, 17, 0, 0, 0, 6, 74, 197, 170, 2, 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