Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4dd9aaed55f0ad463e800856c605752e524acc6401a8de0377157b1110b66c28

Tx prefix hash: b6778f237d0e6e18113e95fa91d1696bba8b148916d5f93b9471aa70ce1a9179
Tx public key: a8e95e4ab44eb481cac226b6bc0fd3db9b6c70c482f59033fff79fed09704c60
Timestamp: 1729664901 Timestamp [UCT]: 2024-10-23 06:28:21 Age [y:d:h:m:s]: 00:035:23:18:07
Block: 1137651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 25697 RingCT/type: yes/0
Extra: 01a8e95e4ab44eb481cac226b6bc0fd3db9b6c70c482f59033fff79fed09704c60021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 93e52faf86c85397a8de2ed2e105b76916d5d5fce64a7789ea73113f117ab76c 0.600000000000 1621182 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": 1137661, "vin": [ { "gen": { "height": 1137651 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93e52faf86c85397a8de2ed2e105b76916d5d5fce64a7789ea73113f117ab76c" } } ], "extra": [ 1, 168, 233, 94, 74, 180, 78, 180, 129, 202, 194, 38, 182, 188, 15, 211, 219, 155, 108, 112, 196, 130, 245, 144, 51, 255, 247, 159, 237, 9, 112, 76, 96, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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