Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3abdb4fa39f77bed7c4a42014fdbcaed0b1b049f60413e5e8736a6503255772

Tx prefix hash: 0258c92518100dbdfba13ae8bb36ce738a41ddf7b695e0a6e52afb0a48b002f1
Tx public key: 890fc2fc7d90306fe6c82534aaf9ae6677cc9e1a746a50858048d2b8f7f687e0
Timestamp: 1594005126 Timestamp [UCT]: 2020-07-06 03:12:06 Age [y:d:h:m:s]: 03:346:16:50:30
Block: 114526 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 931172 RingCT/type: yes/0
Extra: 01890fc2fc7d90306fe6c82534aaf9ae6677cc9e1a746a50858048d2b8f7f687e00211000000024ac5aa02000000000000000000

1 output(s) for total of 256.170172904000 dcy

stealth address amount amount idx
00: e4a1779f6488674d50cfdceee6df1eb5251b42b4a2e8e7be9a954a1f7d5dc304 256.170172904000 196600 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": 114536, "vin": [ { "gen": { "height": 114526 } } ], "vout": [ { "amount": 256170172904, "target": { "key": "e4a1779f6488674d50cfdceee6df1eb5251b42b4a2e8e7be9a954a1f7d5dc304" } } ], "extra": [ 1, 137, 15, 194, 252, 125, 144, 48, 111, 230, 200, 37, 52, 170, 249, 174, 102, 119, 204, 158, 26, 116, 106, 80, 133, 128, 72, 210, 184, 247, 246, 135, 224, 2, 17, 0, 0, 0, 2, 74, 197, 170, 2, 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