Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 124df451dbd9d7513cdef275f2b25ec08656b490fa3da981d53f5f3bcc4b6248

Tx prefix hash: cbee722eb1fe16b6252af6b06f4ad69559e658ac0cfecee2e50ad94499b4bca5
Tx public key: d140c7fd4206d3ff5af746b61614a2037adbcf1c72b22121784261aa077991be
Timestamp: 1590578102 Timestamp [UCT]: 2020-05-27 11:15:02 Age [y:d:h:m:s]: 04:223:15:12:43
Block: 103712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1086731 RingCT/type: yes/0
Extra: 01d140c7fd4206d3ff5af746b61614a2037adbcf1c72b22121784261aa077991be02110000003d8a2ee0d9000000000000000000

1 output(s) for total of 278.201744110000 dcy

stealth address amount amount idx
00: 8fd70675aea2ed38e838e8ff49e309f033cc81620aca2d17574d6670b90089e9 278.201744110000 181877 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": 103722, "vin": [ { "gen": { "height": 103712 } } ], "vout": [ { "amount": 278201744110, "target": { "key": "8fd70675aea2ed38e838e8ff49e309f033cc81620aca2d17574d6670b90089e9" } } ], "extra": [ 1, 209, 64, 199, 253, 66, 6, 211, 255, 90, 247, 70, 182, 22, 20, 162, 3, 122, 219, 207, 28, 114, 178, 33, 33, 120, 66, 97, 170, 7, 121, 145, 190, 2, 17, 0, 0, 0, 61, 138, 46, 224, 217, 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