Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e3926dd4dc70138837a6cb8b686de0f2809d515126d07f1524dd43ac4940d0e

Tx prefix hash: 9ef3d60c51fc732f5ac980bb53b373e6a0fbf194ae7774467ab2e3b0084bb548
Tx public key: d5063843696eac502a0df18fb8bd185970e9e2340bbae2a06e23e8090faeecb0
Timestamp: 1706111748 Timestamp [UCT]: 2024-01-24 15:55:48 Age [y:d:h:m:s]: 01:084:15:49:42
Block: 942389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321610 RingCT/type: yes/0
Extra: 01d5063843696eac502a0df18fb8bd185970e9e2340bbae2a06e23e8090faeecb00211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc87025fa70cbd6fab96e1bbcd01329eeb85847eaa367a96f405cb4eaa0aab0b 0.600000000000 1400559 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": 942399, "vin": [ { "gen": { "height": 942389 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc87025fa70cbd6fab96e1bbcd01329eeb85847eaa367a96f405cb4eaa0aab0b" } } ], "extra": [ 1, 213, 6, 56, 67, 105, 110, 172, 80, 42, 13, 241, 143, 184, 189, 24, 89, 112, 233, 226, 52, 11, 186, 226, 160, 110, 35, 232, 9, 15, 174, 236, 176, 2, 17, 0, 0, 0, 5, 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