Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d35b69bee891b5fcb23ae22364d34047eeca669ee59e21141f66eadf8a974dd

Tx prefix hash: c57f94ebbf185602597d7780b7e91faa3c1ff92806720f62d3cf90c808bc5a1b
Tx public key: 7beb88d98f0b9caae77f7052fdc5597bac4eb3ba3cbdf9e0bf434110e02f99a2
Timestamp: 1581091828 Timestamp [UCT]: 2020-02-07 16:10:28 Age [y:d:h:m:s]: 04:323:15:50:41
Block: 60729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1122726 RingCT/type: yes/0
Extra: 017beb88d98f0b9caae77f7052fdc5597bac4eb3ba3cbdf9e0bf434110e02f99a20211000000044ac5aa02000000000000000000

1 output(s) for total of 386.171687952000 dcy

stealth address amount amount idx
00: 4b7e3c46298f1fb8782227ca4fa41a51225312a6ab9de3622aa6e23f01154876 386.171687952000 111796 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": 60739, "vin": [ { "gen": { "height": 60729 } } ], "vout": [ { "amount": 386171687952, "target": { "key": "4b7e3c46298f1fb8782227ca4fa41a51225312a6ab9de3622aa6e23f01154876" } } ], "extra": [ 1, 123, 235, 136, 217, 143, 11, 156, 170, 231, 127, 112, 82, 253, 197, 89, 123, 172, 78, 179, 186, 60, 189, 249, 224, 191, 67, 65, 16, 224, 47, 153, 162, 2, 17, 0, 0, 0, 4, 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