Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5095e393b58b0c1f6920291a38054dc0e55bf6e35d427108e87f7592a97c591f

Tx prefix hash: 763fd4d3c57ca9d87cfc88eca08addc91fadb338842d4ba808e024da7965e7fa
Tx public key: d7c18c28fa51662dca21b39cf70fde662e1d01673f6a30bcc2b95966624a9f3b
Timestamp: 1709568904 Timestamp [UCT]: 2024-03-04 16:15:04 Age [y:d:h:m:s]: 00:326:04:25:28
Block: 971082 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233436 RingCT/type: yes/0
Extra: 01d7c18c28fa51662dca21b39cf70fde662e1d01673f6a30bcc2b95966624a9f3b0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4302873cdc957a98bb345a01b6d0cf9e769544410e839d21c25c08a4eb181684 0.600000000000 1430957 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": 971092, "vin": [ { "gen": { "height": 971082 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4302873cdc957a98bb345a01b6d0cf9e769544410e839d21c25c08a4eb181684" } } ], "extra": [ 1, 215, 193, 140, 40, 250, 81, 102, 45, 202, 33, 179, 156, 247, 15, 222, 102, 46, 29, 1, 103, 63, 106, 48, 188, 194, 185, 89, 102, 98, 74, 159, 59, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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