Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: daa249d578d52d796464f9a4f6749822e46dff4d9966bc1fcd3af4a548716106

Tx prefix hash: 32bcf9f5a119488c7b88494032d71de0bb9729de2901e62846df6d296711a022
Tx public key: 542c2602f431d1be27e477613a8a888d3c1245e1ec1e94904e89697983fdf9d9
Timestamp: 1701234193 Timestamp [UCT]: 2023-11-29 05:03:13 Age [y:d:h:m:s]: 01:053:23:00:02
Block: 901974 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299909 RingCT/type: yes/0
Extra: 01542c2602f431d1be27e477613a8a888d3c1245e1ec1e94904e89697983fdf9d90211000000024b8f5122000000000000000000

1 output(s) for total of 0.630065487000 dcy

stealth address amount amount idx
00: d31be14b206877b0e3d6de4d3dbf292402cdd4260f771b79345c354ccc976571 0.630065487000 1358575 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": 901984, "vin": [ { "gen": { "height": 901974 } } ], "vout": [ { "amount": 630065487, "target": { "key": "d31be14b206877b0e3d6de4d3dbf292402cdd4260f771b79345c354ccc976571" } } ], "extra": [ 1, 84, 44, 38, 2, 244, 49, 209, 190, 39, 228, 119, 97, 58, 138, 136, 141, 60, 18, 69, 225, 236, 30, 148, 144, 78, 137, 105, 121, 131, 253, 249, 217, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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