Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7b4400dc6e0ae21468aac7ead2e2bcdc823c9b8aa3bfea2d7709f62f2bc86a8

Tx prefix hash: 566b25ee1423a93c1171b45c93c7c95adefed9955be1924e08fb41afd8718856
Tx public key: 0af5d8e1e532ca79e1abf10d57aee3f064ddb79cbf553a35c9634b773c769f68
Timestamp: 1581825324 Timestamp [UCT]: 2020-02-16 03:55:24 Age [y:d:h:m:s]: 04:317:22:28:48
Block: 66163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1119263 RingCT/type: yes/0
Extra: 010af5d8e1e532ca79e1abf10d57aee3f064ddb79cbf553a35c9634b773c769f680211000000037adf42d3000000000000000000

1 output(s) for total of 370.489005667000 dcy

stealth address amount amount idx
00: 588ca26dda0f5ea2a5d207acd64b844a1f40ab71c34213728342baff3b14949c 370.489005667000 121822 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": 66173, "vin": [ { "gen": { "height": 66163 } } ], "vout": [ { "amount": 370489005667, "target": { "key": "588ca26dda0f5ea2a5d207acd64b844a1f40ab71c34213728342baff3b14949c" } } ], "extra": [ 1, 10, 245, 216, 225, 229, 50, 202, 121, 225, 171, 241, 13, 87, 174, 227, 240, 100, 221, 183, 156, 191, 85, 58, 53, 201, 99, 75, 119, 60, 118, 159, 104, 2, 17, 0, 0, 0, 3, 122, 223, 66, 211, 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