Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e06352c59e5413fb4502485cb9d244b54d8dd1a1570e9f104f9b2a47a9c0a643

Tx prefix hash: 5f6306641ea4aa5f8fef9aa204e68f9e9ef06ac48d835cd4cff7ae7ca34c4d9e
Tx public key: edca6cfbeef114bb094f3b29cfab7cad4aafb4439e220d20392f2d8dc77dafa5
Timestamp: 1702975841 Timestamp [UCT]: 2023-12-19 08:50:41 Age [y:d:h:m:s]: 01:104:16:24:13
Block: 916422 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335928 RingCT/type: yes/0
Extra: 01edca6cfbeef114bb094f3b29cfab7cad4aafb4439e220d20392f2d8dc77dafa5021100000001c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d84bac3a62cf55b93517a57f236340268ea32ce4c0231e8005fedcc7e6889512 0.600000000000 1373972 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": 916432, "vin": [ { "gen": { "height": 916422 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d84bac3a62cf55b93517a57f236340268ea32ce4c0231e8005fedcc7e6889512" } } ], "extra": [ 1, 237, 202, 108, 251, 238, 241, 20, 187, 9, 79, 59, 41, 207, 171, 124, 173, 74, 175, 180, 67, 158, 34, 13, 32, 57, 47, 45, 141, 199, 125, 175, 165, 2, 17, 0, 0, 0, 1, 197, 69, 41, 96, 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