Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c257f0bb8e179e0d835753ce205494870baea7548ca98a3a7da8377e7adfb08e

Tx prefix hash: 289cbd56aea5dbb4926e9fe766eedc944895cd9fae127b5d3c40689c3c37a92c
Tx public key: fe5e8b43a4165a72bca1c91ff80ea9f72e13e0045f353d323f11fde3f25e7411
Timestamp: 1581368132 Timestamp [UCT]: 2020-02-10 20:55:32 Age [y:d:h:m:s]: 04:326:10:55:30
Block: 62334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1125395 RingCT/type: yes/0
Extra: 01fe5e8b43a4165a72bca1c91ff80ea9f72e13e0045f353d323f11fde3f25e7411021100000003d81c26c0000000000000000000

1 output(s) for total of 381.471763314000 dcy

stealth address amount amount idx
00: 371bf6f1747c1adeadec18e0f821a6ef3671683efb79e1f2915c3d305139e20e 381.471763314000 114949 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": 62344, "vin": [ { "gen": { "height": 62334 } } ], "vout": [ { "amount": 381471763314, "target": { "key": "371bf6f1747c1adeadec18e0f821a6ef3671683efb79e1f2915c3d305139e20e" } } ], "extra": [ 1, 254, 94, 139, 67, 164, 22, 90, 114, 188, 161, 201, 31, 248, 14, 169, 247, 46, 19, 224, 4, 95, 53, 61, 50, 63, 17, 253, 227, 242, 94, 116, 17, 2, 17, 0, 0, 0, 3, 216, 28, 38, 192, 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