Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a60f4be6e0951853c8010b5705238653e000fad22fd9b88c715a8b25148c057

Tx prefix hash: 8b60e1c590cf2c0fc628fbac1a812b3206366a2dcf2f79825e5a19255ee13dd8
Tx public key: 910a40554052a9657d3eb809bc3a06472c09be4df54cb2c8114af77c62b72dd9
Timestamp: 1710687017 Timestamp [UCT]: 2024-03-17 14:50:17 Age [y:d:h:m:s]: 01:040:22:25:32
Block: 980365 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290242 RingCT/type: yes/0
Extra: 01910a40554052a9657d3eb809bc3a06472c09be4df54cb2c8114af77c62b72dd902110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a500bea2e71f3e5fcefe035479d8a434540d3ce8879576c0344fbb9a058431d 0.600000000000 1440430 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": 980375, "vin": [ { "gen": { "height": 980365 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a500bea2e71f3e5fcefe035479d8a434540d3ce8879576c0344fbb9a058431d" } } ], "extra": [ 1, 145, 10, 64, 85, 64, 82, 169, 101, 125, 62, 184, 9, 188, 58, 6, 71, 44, 9, 190, 77, 245, 76, 178, 200, 17, 74, 247, 124, 98, 183, 45, 217, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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