Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4927437291e8ecdf854ad97efb8ea778bac431968f8f49f5b6dc31cb7d0c660f

Tx prefix hash: a2bdd118f47ddf482d45fd5fcdcc4646820959d4fe9af9b1135f399d4aedb7a6
Tx public key: efce711c31fd1ed21284c16dac7d96b91b0be60fea486b653818ed10dd077932
Timestamp: 1672558910 Timestamp [UCT]: 2023-01-01 07:41:50 Age [y:d:h:m:s]: 02:055:19:32:12
Block: 665107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 561545 RingCT/type: yes/0
Extra: 01efce711c31fd1ed21284c16dac7d96b91b0be60fea486b653818ed10dd07793202110000000152542ceb000000000000000000

1 output(s) for total of 3.839055356000 dcy

stealth address amount amount idx
00: e826ce4a04f0bd74df72f340e410b0531abf041148fd3d3737ba0ee82c447778 3.839055356000 1106122 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": 665117, "vin": [ { "gen": { "height": 665107 } } ], "vout": [ { "amount": 3839055356, "target": { "key": "e826ce4a04f0bd74df72f340e410b0531abf041148fd3d3737ba0ee82c447778" } } ], "extra": [ 1, 239, 206, 113, 28, 49, 253, 30, 210, 18, 132, 193, 109, 172, 125, 150, 185, 27, 11, 230, 15, 234, 72, 107, 101, 56, 24, 237, 16, 221, 7, 121, 50, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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