Read the type in context
The ethereum.org transaction documentation describes Type 0 as the legacy format, Type 1 as the access-list format and Type 2 as the dynamic-fee format associated with EIP-1559. These labels help explain which fields the transaction uses; they are not a ranking of the recipient’s honesty.
Compare fields that have the same meaning
When two transaction views show different fee fields, check their format before treating a missing field as missing payment evidence. For example, the dynamic-fee format includes maximum-fee and priority-fee fields that are not the same layout as a legacy gas price. Use the actual receipt and execution status for outcome questions.
Do not approve based on a type number
A recognised format does not validate the business behind a transaction or make signing safe. coinscammercheck is a beta address-risk service, not a guarantee about every requested signature; no detected risk does not mean safety. Official transaction documentation checked 25 October 2026.
Sources · checked 25 October 2026
https://coinscammercheck.supermankorea.xyz/
https://ethereum.org/en/developers/docs/transactions/