Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d82b0c798f302468b1936ff41661aeb475a8df762a9c7d364f165388b90b7cda

Tx prefix hash: ebbca16b3b241c781fb43f00d31be16d9b0a93e053ae4979002906ace5acf29f
Tx public key: dd386c14d063893e83cc3fdbeb2ec3a40e591944462fd0c6de23a72a84e02ac2
Timestamp: 1722763422 Timestamp [UCT]: 2024-08-04 09:23:42 Age [y:d:h:m:s]: 00:255:20:49:51
Block: 1080458 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182777 RingCT/type: yes/0
Extra: 01dd386c14d063893e83cc3fdbeb2ec3a40e591944462fd0c6de23a72a84e02ac2021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fbd994c24b1d4b3af5381c89334e7f9ec8a3ff403d89471a4a1e6bcacb9fa75c 0.600000000000 1553823 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": 1080468, "vin": [ { "gen": { "height": 1080458 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fbd994c24b1d4b3af5381c89334e7f9ec8a3ff403d89471a4a1e6bcacb9fa75c" } } ], "extra": [ 1, 221, 56, 108, 20, 208, 99, 137, 62, 131, 204, 63, 219, 235, 46, 195, 164, 14, 89, 25, 68, 70, 47, 208, 198, 222, 35, 167, 42, 132, 224, 42, 194, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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