Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59a6243f5d9deec6ce4d77e6af6e78fd91084f67f3bbf6cda14e8bcdfb046bb2

Tx prefix hash: d346bb0a74304b0ac814616b536736e2e22b77fcf2945efb5f7c35a8ba5c207e
Tx public key: b20478a9de54ee594698c4441cdf012d4931ef8a39da45fbc956b39aabfbd684
Timestamp: 1684579707 Timestamp [UCT]: 2023-05-20 10:48:27 Age [y:d:h:m:s]: 01:324:15:10:14
Block: 764163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 493218 RingCT/type: yes/0
Extra: 01b20478a9de54ee594698c4441cdf012d4931ef8a39da45fbc956b39aabfbd68402110000000333af99f4000000000000000000

1 output(s) for total of 1.803063178000 dcy

stealth address amount amount idx
00: 5ea1d65695f4ff142c8b7def6442320cc6a05d907c607c4e6a1e6551141ab2d9 1.803063178000 1213060 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": 764173, "vin": [ { "gen": { "height": 764163 } } ], "vout": [ { "amount": 1803063178, "target": { "key": "5ea1d65695f4ff142c8b7def6442320cc6a05d907c607c4e6a1e6551141ab2d9" } } ], "extra": [ 1, 178, 4, 120, 169, 222, 84, 238, 89, 70, 152, 196, 68, 28, 223, 1, 45, 73, 49, 239, 138, 57, 218, 69, 251, 201, 86, 179, 154, 171, 251, 214, 132, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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