Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a6464b1fdd294598a319e41dea60677abda2b1117f3a430f67b1da2938e1aa7

Tx prefix hash: fa77f5edfe48769294fe5f8bb7dd8efaa6b14a329025dc6ec528d4c34b9140ce
Tx public key: fc084c1c2de9e47964a13fc5327fbfa650b3fd22170b1e78a725901456090375
Timestamp: 1728901925 Timestamp [UCT]: 2024-10-14 10:32:05 Age [y:d:h:m:s]: 00:174:06:38:37
Block: 1131363 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124318 RingCT/type: yes/0
Extra: 01fc084c1c2de9e47964a13fc5327fbfa650b3fd22170b1e78a725901456090375021100000004e914dd15000000000000000000

1 output(s) for total of 0.600010000000 dcy

stealth address amount amount idx
00: 9d3193a381bda620c8a1189e5f9ef14799c002c8c50d60b25f1a71e34d8bcacb 0.600010000000 1614260 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": 1131373, "vin": [ { "gen": { "height": 1131363 } } ], "vout": [ { "amount": 600010000, "target": { "key": "9d3193a381bda620c8a1189e5f9ef14799c002c8c50d60b25f1a71e34d8bcacb" } } ], "extra": [ 1, 252, 8, 76, 28, 45, 233, 228, 121, 100, 161, 63, 197, 50, 127, 191, 166, 80, 179, 253, 34, 23, 11, 30, 120, 167, 37, 144, 20, 86, 9, 3, 117, 2, 17, 0, 0, 0, 4, 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