Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eeb9d9678351efcbdfb26d277b57eb8d7ff9965e092451398667aa22de2d2d9e

Tx prefix hash: fa12dd1db383638a804599f9ed5161db3fecf9c60b5b4163ac234d3c16e2fa09
Tx public key: d086158a0c91c513652f896fb46c69e5ee12ef39bd9e66eff46e08b3be214750
Timestamp: 1577181497 Timestamp [UCT]: 2019-12-24 09:58:17 Age [y:d:h:m:s]: 05:071:21:52:32
Block: 30569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1201246 RingCT/type: yes/0
Extra: 01d086158a0c91c513652f896fb46c69e5ee12ef39bd9e66eff46e08b3be214750021100000001d81c26c0000000000000000000

1 output(s) for total of 486.085957164000 dcy

stealth address amount amount idx
00: 8c144ed5f8e5399086601e97b9ad7eb741c9803b536ade11cf027102a80fd7ca 486.085957164000 50477 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": 30579, "vin": [ { "gen": { "height": 30569 } } ], "vout": [ { "amount": 486085957164, "target": { "key": "8c144ed5f8e5399086601e97b9ad7eb741c9803b536ade11cf027102a80fd7ca" } } ], "extra": [ 1, 208, 134, 21, 138, 12, 145, 197, 19, 101, 47, 137, 111, 180, 108, 105, 229, 238, 18, 239, 57, 189, 158, 102, 239, 244, 110, 8, 179, 190, 33, 71, 80, 2, 17, 0, 0, 0, 1, 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