Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0f842c7211e0f39d30845dfdee14b4b61832940af6773d8719bf046928ec61f

Tx prefix hash: 1e110d9f6e537a6a12f681ffb815681e89a9c077ed12b4dadc1fe4125753cb0e
Tx public key: 4ee708d20c4c392d906d44aa41b7581ad3ae90086feda576f070b2570378c8d5
Timestamp: 1717120196 Timestamp [UCT]: 2024-05-31 01:49:56 Age [y:d:h:m:s]: 01:185:23:28:14
Block: 1033687 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391534 RingCT/type: yes/0
Extra: 014ee708d20c4c392d906d44aa41b7581ad3ae90086feda576f070b2570378c8d502110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5cc05c2714343a6659f26fe1782f92d30e4bdccbc852767c7fc9abfe46289c1e 0.600000000000 1502158 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": 1033697, "vin": [ { "gen": { "height": 1033687 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5cc05c2714343a6659f26fe1782f92d30e4bdccbc852767c7fc9abfe46289c1e" } } ], "extra": [ 1, 78, 231, 8, 210, 12, 76, 57, 45, 144, 109, 68, 170, 65, 183, 88, 26, 211, 174, 144, 8, 111, 237, 165, 118, 240, 112, 178, 87, 3, 120, 200, 213, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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