├── LICENSE-APACHE
├── LICENSE-MIT
└── README.md
/LICENSE-APACHE:
--------------------------------------------------------------------------------
1 | Apache License
2 | Version 2.0, January 2004
3 | http://www.apache.org/licenses/
4 |
5 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6 |
7 | 1. Definitions.
8 |
9 | "License" shall mean the terms and conditions for use, reproduction,
10 | and distribution as defined by Sections 1 through 9 of this document.
11 |
12 | "Licensor" shall mean the copyright owner or entity authorized by
13 | the copyright owner that is granting the License.
14 |
15 | "Legal Entity" shall mean the union of the acting entity and all
16 | other entities that control, are controlled by, or are under common
17 | control with that entity. For the purposes of this definition,
18 | "control" means (i) the power, direct or indirect, to cause the
19 | direction or management of such entity, whether by contract or
20 | otherwise, or (ii) ownership of fifty percent (50%) or more of the
21 | outstanding shares, or (iii) beneficial ownership of such entity.
22 |
23 | "You" (or "Your") shall mean an individual or Legal Entity
24 | exercising permissions granted by this License.
25 |
26 | "Source" form shall mean the preferred form for making modifications,
27 | including but not limited to software source code, documentation
28 | source, and configuration files.
29 |
30 | "Object" form shall mean any form resulting from mechanical
31 | transformation or translation of a Source form, including but
32 | not limited to compiled object code, generated documentation,
33 | and conversions to other media types.
34 |
35 | "Work" shall mean the work of authorship, whether in Source or
36 | Object form, made available under the License, as indicated by a
37 | copyright notice that is included in or attached to the work
38 | (an example is provided in the Appendix below).
39 |
40 | "Derivative Works" shall mean any work, whether in Source or Object
41 | form, that is based on (or derived from) the Work and for which the
42 | editorial revisions, annotations, elaborations, or other modifications
43 | represent, as a whole, an original work of authorship. For the purposes
44 | of this License, Derivative Works shall not include works that remain
45 | separable from, or merely link (or bind by name) to the interfaces of,
46 | the Work and Derivative Works thereof.
47 |
48 | "Contribution" shall mean any work of authorship, including
49 | the original version of the Work and any modifications or additions
50 | to that Work or Derivative Works thereof, that is intentionally
51 | submitted to Licensor for inclusion in the Work by the copyright owner
52 | or by an individual or Legal Entity authorized to submit on behalf of
53 | the copyright owner. For the purposes of this definition, "submitted"
54 | means any form of electronic, verbal, or written communication sent
55 | to the Licensor or its representatives, including but not limited to
56 | communication on electronic mailing lists, source code control systems,
57 | and issue tracking systems that are managed by, or on behalf of, the
58 | Licensor for the purpose of discussing and improving the Work, but
59 | excluding communication that is conspicuously marked or otherwise
60 | designated in writing by the copyright owner as "Not a Contribution."
61 |
62 | "Contributor" shall mean Licensor and any individual or Legal Entity
63 | on behalf of whom a Contribution has been received by Licensor and
64 | subsequently incorporated within the Work.
65 |
66 | 2. Grant of Copyright License. Subject to the terms and conditions of
67 | this License, each Contributor hereby grants to You a perpetual,
68 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69 | copyright license to reproduce, prepare Derivative Works of,
70 | publicly display, publicly perform, sublicense, and distribute the
71 | Work and such Derivative Works in Source or Object form.
72 |
73 | 3. Grant of Patent License. Subject to the terms and conditions of
74 | this License, each Contributor hereby grants to You a perpetual,
75 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76 | (except as stated in this section) patent license to make, have made,
77 | use, offer to sell, sell, import, and otherwise transfer the Work,
78 | where such license applies only to those patent claims licensable
79 | by such Contributor that are necessarily infringed by their
80 | Contribution(s) alone or by combination of their Contribution(s)
81 | with the Work to which such Contribution(s) was submitted. If You
82 | institute patent litigation against any entity (including a
83 | cross-claim or counterclaim in a lawsuit) alleging that the Work
84 | or a Contribution incorporated within the Work constitutes direct
85 | or contributory patent infringement, then any patent licenses
86 | granted to You under this License for that Work shall terminate
87 | as of the date such litigation is filed.
88 |
89 | 4. Redistribution. You may reproduce and distribute copies of the
90 | Work or Derivative Works thereof in any medium, with or without
91 | modifications, and in Source or Object form, provided that You
92 | meet the following conditions:
93 |
94 | (a) You must give any other recipients of the Work or
95 | Derivative Works a copy of this License; and
96 |
97 | (b) You must cause any modified files to carry prominent notices
98 | stating that You changed the files; and
99 |
100 | (c) You must retain, in the Source form of any Derivative Works
101 | that You distribute, all copyright, patent, trademark, and
102 | attribution notices from the Source form of the Work,
103 | excluding those notices that do not pertain to any part of
104 | the Derivative Works; and
105 |
106 | (d) If the Work includes a "NOTICE" text file as part of its
107 | distribution, then any Derivative Works that You distribute must
108 | include a readable copy of the attribution notices contained
109 | within such NOTICE file, excluding those notices that do not
110 | pertain to any part of the Derivative Works, in at least one
111 | of the following places: within a NOTICE text file distributed
112 | as part of the Derivative Works; within the Source form or
113 | documentation, if provided along with the Derivative Works; or,
114 | within a display generated by the Derivative Works, if and
115 | wherever such third-party notices normally appear. The contents
116 | of the NOTICE file are for informational purposes only and
117 | do not modify the License. You may add Your own attribution
118 | notices within Derivative Works that You distribute, alongside
119 | or as an addendum to the NOTICE text from the Work, provided
120 | that such additional attribution notices cannot be construed
121 | as modifying the License.
122 |
123 | You may add Your own copyright statement to Your modifications and
124 | may provide additional or different license terms and conditions
125 | for use, reproduction, or distribution of Your modifications, or
126 | for any such Derivative Works as a whole, provided Your use,
127 | reproduction, and distribution of the Work otherwise complies with
128 | the conditions stated in this License.
129 |
130 | 5. Submission of Contributions. Unless You explicitly state otherwise,
131 | any Contribution intentionally submitted for inclusion in the Work
132 | by You to the Licensor shall be under the terms and conditions of
133 | this License, without any additional terms or conditions.
134 | Notwithstanding the above, nothing herein shall supersede or modify
135 | the terms of any separate license agreement you may have executed
136 | with Licensor regarding such Contributions.
137 |
138 | 6. Trademarks. This License does not grant permission to use the trade
139 | names, trademarks, service marks, or product names of the Licensor,
140 | except as required for reasonable and customary use in describing the
141 | origin of the Work and reproducing the content of the NOTICE file.
142 |
143 | 7. Disclaimer of Warranty. Unless required by applicable law or
144 | agreed to in writing, Licensor provides the Work (and each
145 | Contributor provides its Contributions) on an "AS IS" BASIS,
146 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147 | implied, including, without limitation, any warranties or conditions
148 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149 | PARTICULAR PURPOSE. You are solely responsible for determining the
150 | appropriateness of using or redistributing the Work and assume any
151 | risks associated with Your exercise of permissions under this License.
152 |
153 | 8. Limitation of Liability. In no event and under no legal theory,
154 | whether in tort (including negligence), contract, or otherwise,
155 | unless required by applicable law (such as deliberate and grossly
156 | negligent acts) or agreed to in writing, shall any Contributor be
157 | liable to You for damages, including any direct, indirect, special,
158 | incidental, or consequential damages of any character arising as a
159 | result of this License or out of the use or inability to use the
160 | Work (including but not limited to damages for loss of goodwill,
161 | work stoppage, computer failure or malfunction, or any and all
162 | other commercial damages or losses), even if such Contributor
163 | has been advised of the possibility of such damages.
164 |
165 | 9. Accepting Warranty or Additional Liability. While redistributing
166 | the Work or Derivative Works thereof, You may choose to offer,
167 | and charge a fee for, acceptance of support, warranty, indemnity,
168 | or other liability obligations and/or rights consistent with this
169 | License. However, in accepting such obligations, You may act only
170 | on Your own behalf and on Your sole responsibility, not on behalf
171 | of any other Contributor, and only if You agree to indemnify,
172 | defend, and hold each Contributor harmless for any liability
173 | incurred by, or claims asserted against, such Contributor by reason
174 | of your accepting any such warranty or additional liability.
175 |
176 | END OF TERMS AND CONDITIONS
177 |
178 | APPENDIX: How to apply the Apache License to your work.
179 |
180 | To apply the Apache License to your work, attach the following
181 | boilerplate notice, with the fields enclosed by brackets "[]"
182 | replaced with your own identifying information. (Don't include
183 | the brackets!) The text should be enclosed in the appropriate
184 | comment syntax for the file format. We also recommend that a
185 | file or class name and description of purpose be included on the
186 | same "printed page" as the copyright notice for easier
187 | identification within third-party archives.
188 |
189 | Copyright [yyyy] [name of copyright owner]
190 |
191 | Licensed under the Apache License, Version 2.0 (the "License");
192 | you may not use this file except in compliance with the License.
193 | You may obtain a copy of the License at
194 |
195 | http://www.apache.org/licenses/LICENSE-2.0
196 |
197 | Unless required by applicable law or agreed to in writing, software
198 | distributed under the License is distributed on an "AS IS" BASIS,
199 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
200 | See the License for the specific language governing permissions and
201 | limitations under the License.
202 |
--------------------------------------------------------------------------------
/LICENSE-MIT:
--------------------------------------------------------------------------------
1 | The MIT License (MIT)
2 |
3 | Copyright (c) 2022-2023 Ultimate EVM Tracing Reference Contributors
4 |
5 | Permission is hereby granted, free of charge, to any person obtaining a copy
6 | of this software and associated documentation files (the "Software"), to deal
7 | in the Software without restriction, including without limitation the rights
8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9 | copies of the Software, and to permit persons to whom the Software is
10 | furnished to do so, subject to the following conditions:
11 |
12 | The above copyright notice and this permission notice shall be included in
13 | all copies or substantial portions of the Software.
14 |
15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
21 | THE SOFTWARE.
22 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | # Ultimate EVM Tracing Reference
2 |
3 | [](https://t.me/paradigm_data)
4 |
5 | This repo is a collection of trace-related information for easy reference.
6 |
7 | A best effort is made to provide accurate information. Please submit corrections to the issue tracker.
8 |
9 | ## Contents
10 | 1. [Tracers](#tracers)
11 | 2. [Trace Methods](#trace-methods)
12 | 3. [Node Client Support](#node-client-support)
13 | 4. [RPC Provider Support](#rpc-provider-support)
14 | 5. [Ecosystem Tooling Support](#ecosystem-tooling-support)
15 | 6. [Hosted Data Platform Support](#hosted-data-platform-support)
16 | 7. [Example Tracer Data](#example-tracer-data)
17 |
18 | ## Tracers
19 |
20 | A tracer gives a detailed view into what happened during a block or transaction.
21 |
22 | Each tracer type provides a different set of information. There are two main categories of tracers, parity and geth. Each node client supports these tracer types to varying degrees.
23 |
24 | **To see the specific information returned by each tracer, see the schemas and data samples in the [Example Tracer Data](#example-tracer-data) below.**
25 |
26 | | tracer | description | parameters |
27 | | --: | --- | --- |
28 | | [`parity calls`1](https://openethereum.github.io/JSONRPC-trace-module) | calls in a flat list structure | `[ "trace" ]` |
29 | | [`parity stateDiffs`2](https://openethereum.github.io/JSONRPC-trace-module) | all state changes for each tx | `[ "stateDiff" ]` |
30 | | [`parity vmTraces`](https://openethereum.github.io/JSONRPC-trace-module) | opcode-level trace | `[ "vmTrace" ]` |
31 | | [`geth opcodes`](https://geth.ethereum.org/docs/developers/evm-tracing/built-in-tracers#struct-opcode-logger) | opcode-level trace | `{ }` |
32 | | [`geth calls`1](https://geth.ethereum.org/docs/developers/evm-tracing/built-in-tracers#call-tracer) | calls in a nested structure | `{ "tracer": "callTracer" }` |
33 | | [`geth preState`2](https://geth.ethereum.org/docs/developers/evm-tracing/built-in-tracers#prestate-tracer) | data that was read before each tx | `{ "tracer": "prestateTracer" }` |
34 | | [`geth stateDiffs`2](https://geth.ethereum.org/docs/developers/evm-tracing/built-in-tracers#prestate-tracer) | all state changes for each tx | `{ "tracer": "prestateTracer", "diffMode": true }` |
35 | | [`geth 4byte`](https://geth.ethereum.org/docs/developers/evm-tracing/built-in-tracers#4byte-tracer) | 4byte prefixes of function calls | `{ "tracer": "4byteTracer" }` |
36 | | [`geth javascript`3](https://geth.ethereum.org/docs/developers/evm-tracing/custom-tracer#custom-javascript-tracing) | custom javascript tracer functions | `{ "tracer": "{ fault: ..., result: ... }" }` |
37 |
38 | *1: Geth call traces contain nearly identical information to Parity call traces. There are differences such as 1) they include precompile calls, 2) they used a nested schema instead of a list, 3) they do not include block rewards. See [here](https://github.com/blockchain-etl/ethereum-etl/blob/develop/docs/schema.md#differences-between-geth-and-parity-tracescsv) for additional differences.*
39 |
40 | *2: There are four types of state changes: balances, codes, nonces, and storage. State-related traces include information about all four.*
41 |
42 | *3: "tracer is interpreted as a JavaScript expression that is expected to evaluate to an object which must expose the result and fault methods. There exist 4 additional methods, namely: setup, step, enter, and exit. enter and exit must be present or omitted together."*
43 |
44 | ## Trace Methods
45 |
46 | RPC methods are used to obtain trace data from RPC endpoints.
47 |
48 | Each method applies one or more tracers to a particular scope of data, such as a block, transaction, or call data.
49 |
50 | | rpc method | description | tracers |
51 | | --: | --- | --- |
52 | | `trace_block` | basic block trace | parity calls
53 | | `trace_transaction` | basic transaction trace | parity calls
54 | | `trace_replayBlockTransactions` | advanced block trace | all parity tracers
55 | | `trace_replayTransaction` | advanced transaction trace | all parity tracers
56 | | `trace_filter` | query a subset of traces | all parity tracers
57 | | `trace_call` | trace custom call_data | all parity tracers
58 | | `trace_callMany` | trace sequence of call_data | all parity tracers
59 | | `trace_rawTransaction` | parity call_data trace | all parity tracers
60 | | `trace_get` | parity indexed trace | parity calls
61 | | `debug_traceBlock` | advanced block trace | all geth tracers
62 | | `debug_traceTransaction` | basic transaction trace | all geth tracers
63 | | `debug_traceCall` | trace custom call_data | all geth tracers
64 | | `debug_traceBlockByNumber` | advanced block trace | all geth tracers
65 | | `debug_traceBlockByHash` | advanced block trace | all geth tracers
66 |
67 | ## Node Client Support
68 |
69 | Node clients track the state of the chain and can perform tracing on the chain's history.
70 |
71 | Each node client supports a different set of tracers and trace methods.
72 |
73 | | rpc method | [geth](https://geth.ethereum.org/docs/developers/evm-tracing/built-in-tracers) | [reth](https://paradigmxyz.github.io/reth/jsonrpc/intro.html) | [erigon](https://github.com/ledgerwatch/erigon/blob/devel/cmd/rpcdaemon/README.md) | [besu](https://besu.hyperledger.org/public-networks/reference/api) | [nethermind](https://docs.nethermind.io/interacting/json-rpc-ns/trace) |
74 | | --: | :-: | :-: | :-: | :-: | :-: |
75 | | `trace_block` | ❌ | ✅ | ✅ | ✅ | ✅ |
76 | | `trace_transaction` | ❌ | ✅ | ✅ | ✅ | ✅ |
77 | | `trace_replayBlockTransactions` | ❌ | ✅ | ✅ | ✅ | ✅ |
78 | | `trace_replayTransaction` | ❌ | ✅ | ✅ | ❌ | ✅ |
79 | | `trace_filter` | ❌ | ✅ | ✅ | ✅ | ✅ |
80 | | `trace_call` | ❌ | ✅ | ✅ | ✅ | ✅ |
81 | | `trace_callMany` | ❌ | ✅ | ✅ | ✅ | ❌ |
82 | | `trace_rawTransaction` | ❌ | ✅ | ✅ | ✅ | ✅ |
83 | | `trace_get` | ❌ | ✅ | ✅ | ✅ | ❌ |
84 | | `debug_traceBlock` | ✅ | ✅ | ✅ | ✅ | ✅ |
85 | | `debug_traceTransaction` | ✅ | ✅ | ✅ | ❌ | ✅ |
86 | | `debug_traceCall` | ✅ | ✅ | ✅ | ❌ | ✅ |
87 | | `debug_traceBlockByNumber` | ✅ | ✅ | ✅ | ❌ | ✅ |
88 | | `debug_traceBlockByHash` | ✅ | ✅ | ✅ | ✅ | ✅ |
89 |
90 | The set of traces that can be obtained for a chain is determined by the clients that support that chain:
91 |
92 | | rpc method | geth | reth | [erigon](https://github.com/ledgerwatch/erigon#system-requirements) | [besu](https://besu.hyperledger.org/public-networks/get-started/connect/mainnet) | [nethermind](https://www.quicknode.com/guides/infrastructure/node-setup/how-to-run-nethermind-node) | geth fork |
93 | | --: | :-: | :-: | :-: | :-: | :-: | :-: |
94 | | ethereum | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ |
95 | | goerli | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ |
96 | | [arbitrum](https://docs.arbitrum.io/node-running/how-tos/running-a-full-node) | ❌ | ❌ | ❌ | ❌ | ❌ | ✅ |
97 | | [optimism](https://community.optimism.io/docs/developers/bedrock/node-operator-guide/) | ❌ | ✅ | ❌ | ❌ | ❌ | ✅ |
98 | | zora | ❌ | ✅ | ❌ | ❌ | ❌ | ✅ |
99 | | [base](https://docs.base.org/guides/run-a-base-node/) | ❌ | ✅ | ❌ | ❌ | ❌ | ✅ |
100 | | [polygon](https://wiki.polygon.technology/docs/category/operate-a-node/) | ❌ | ❌ | ✅ | ❌ | ❌ | ✅ |
101 | | [gnosis](https://docs.gnosischain.com/node/manual/execution) | ✅ | ❌ | ✅ | ✅ | ✅ | ❌ |
102 | | [bnb](https://github.com/bnb-chain/bsc) | ❌ | ❌ | ✅[*](https://github.com/node-real/bsc-erigon) | ❌ | ❌ | ✅ |
103 |
104 |
105 | ## RPC Provider Support
106 |
107 | RPC providers create endpoints where customers can access RPC data without having to run their own nodes.
108 |
109 | Every node provider supports different tracers and trace methods.
110 |
111 | | rpc method | [infura](https://docs.infura.io/networks/ethereum/json-rpc-methods/trace-methods) | [alchemy](https://docs.alchemy.com/reference/trace-api)
([pricing](https://docs.alchemy.com/reference/compute-unit-costs#debug-api)) | [quicknode](https://www.quicknode.com/docs/ethereum)
([pricing](https://www.quicknode.com/api-credits)) | [llamanodes](https://llamanodes.notion.site/Ethereum-Request-Method-Pricing-288b72d56067497c88deddef36dbb19e)
([pricing](https://llamanodes.notion.site/Ethereum-Request-Method-Pricing-288b72d56067497c88deddef36dbb19e)) | [chainstack](https://docs.chainstack.com/docs/debug-and-trace-apis)
([pricing](https://chainstack.com/pricing/)) |
112 | | --: | :-: | :-: | :-: | :-: | :-: |
113 | | `trace_block` | ✅ | ✅ | ✅ | ✅ | ✅ |
114 | | `trace_transaction` | ✅ | ✅ | ✅ | ✅ | ✅ |
115 | | `trace_replayBlockTransactions` | ❌ | ✅ | ✅ | ✅ | ✅ |
116 | | `trace_replayTransaction` | ❌ | ✅ | ✅ | ✅ | ✅ |
117 | | `trace_filter` | ✅ | ✅ | ✅ | ✅ | ✅ |
118 | | `trace_call` | ✅ | ✅ | ✅ | ✅ | ✅ |
119 | | `trace_callMany` | ✅ | ❌ | ✅ | ✅ | ✅ |
120 | | `trace_rawTransaction` | ❌ | ✅ | ✅ | ❌ | ✅ |
121 | | `trace_get` | ❌ | ✅ | ❌ | ✅ | ✅ |
122 | | `debug_traceBlock` | ❌ | ❌ | ✅ | ❌ | ✅ |
123 | | `debug_traceTransaction` | ❌ | ✅ | ✅ | ✅ | ✅ |
124 | | `debug_traceCall` | ❌ | ✅ | ✅ | ✅ | ✅ |
125 | | `debug_traceBlockByNumber` | ❌ | ✅ | ✅ | ✅ | ✅ |
126 | | `debug_traceBlockByHash` | ❌ | ✅ | ✅ | ✅ | ✅ |
127 |
128 | ## Ecosystem Tooling Support
129 |
130 | Many different tools exist for obtaining and analyzing traces.
131 |
132 | Each tool supports a different set of tracers and trace methods. The libraries in the javascript ecosystem generally do not support tracing.
133 |
134 | 📟 = can use from command line
135 | 🐍 = can use as a python library
136 | 🦀 = can use as a rust library
137 |
138 | | tracer | [cryo](https://github.com/paradigmxyz/cryo)
📟🐍🦀 | [ethereum
etl](https://github.com/blockchain-etl/ethereum-etl) 📟 | [ethers.rs](https://github.com/gakonst/ethers-rs)
🦀 | [ctc](https://github.com/checkthechain/checkthechain)
🐍 | [ape](https://github.com/apeworx/evm-trace)
🐍 | [web3py](https://github.com/ethereum/web3.py)
🐍 |
139 | | --: | :-: | :-: | :-: | :-: | :-: | :-: |
140 | | `parity calls` | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
141 | | `parity stateDiffs` | ✅ | ❌ | ✅ | ✅ | ✅ | ✅ |
142 | | `parity vmTraces` | ✅ | ❌ | ✅ | ✅ | ✅ | ✅ |
143 | | `geth opcodes` | ✅ | ❌ | ✅ | ❌ | ✅ | ❌ |
144 | | `geth calls` | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ |
145 | | `geth preState` | ✅ | ❌ | ✅ | ✅ | ✅ | ❌ |
146 | | `geth stateDiffs` | ✅ | ❌ | ✅ | ✅ | ✅ | ❌ |
147 | | `geth 4byte counts` | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ |
148 | | `geth javascript` | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ |
149 |
150 | ## Hosted Data Platform Support
151 |
152 | Hosted data platforms allow customers to interact with trace data directly without running their own infrastructure.
153 |
154 | Most platforms only support call traces.
155 |
156 | | tracer | [Dune](https://dune.com/docs/data-tables/raw/evm/traces/) | [Flipside](https://flipsidecrypto.xyz/) | [Bigquery](https://cloud.google.com/blog/products/data-analytics/ethereum-bigquery-public-dataset-smart-contract-analytics) | [Allium](https://docs.allium.so/data-tables/ethereum/decoded/decoded-traces) |
157 | | --: | :-: | :-: | :-: | :-: |
158 | | `parity calls` | ✅ | ✅ | ✅ | ✅ |
159 | | `parity stateDiffs` | ❌ | ❌ | ❌ | ❌ |
160 | | `parity vmTraces` | ❌ | ❌ | ❌ | ❌ |
161 | | `geth opcodes` | ❌ | ❌ | ❌ | ❌ |
162 | | `geth calls` | ✅ | ✅ | ✅ | ✅ |
163 | | `geth preState` | ❌ | ❌ | ❌ | ❌ |
164 | | `geth state diffs` | ❌ | ❌ | ❌ | ❌ |
165 | | `geth 4byte counts` | ❌ | ❌ | ❌ | ❌ |
166 | | `geth javascript` | ❌ | ❌ | ❌ | ❌ |
167 |
168 | ## Example Tracer Data
169 |
170 | A 100 block sample of data is provided for each tracer (block range 10,000,000 through 10,000,099)
171 |
172 |
tracer | 176 |schema | 177 |data | 178 |collection command | 179 |
---|---|---|---|
parity calls |
184 | schema- action_from: binary |
185 | parquet | 186 |cryo traces -b 10M:+100 |
187 |
parity stateDiffs balances |
191 | schema- transaction_hash: binary |
192 | parquet | 193 |cryo balance_diffs -b 10M:+100 |
194 |
parity stateDiffs codes |
197 | schema- block_number: uint32 |
198 | parquet | 199 |cryo code_diffs -b 10M:+100 |
200 |
parity stateDiffs nonces |
203 | schema- block_number: uint32 |
204 | parquet | 205 |cryo nonce_diffs -b 10M:+100 |
206 |
parity stateDiffs storage |
210 | schema- block_number: uint32 |
211 | parquet | 212 |cryo storage_diffs -b 10M:+100 |
213 |
parity vmTraces |
216 | schema- block_number: uint32 |
217 | parquet | 218 |cryo vm_traces -b 10M:+100 |
219 |
geth opcodes |
222 | schema- block_number: uint32 |
223 | parquet | 224 |cryo geth_opcodes -b 10M:+100 \ --include-columns stack storage |
225 |
geth calls |
228 | schema- typ: string |
229 | parquet | 230 |cryo geth_calls -b 10M:+100 |
231 |
geth prestate balances |
234 | schema- block_number: uint32 |
235 | parquet | 236 |cryo balance_reads -b 10M:+100 |
237 |
geth prestate codes |
240 | schema- block_number: uint32 |
241 | parquet | 242 |cryo code_reads -b 10M:+100 |
243 |
geth prestate nonces |
246 | schema- block_number: uint32 |
247 | parquet | 248 |cryo nonce_reads -b 10M:+100 |
249 |
geth prestate storages |
252 | schema- block_number: uint32 |
253 | parquet | 254 |cryo storage_reads -b 10M:+100 |
255 |
geth stateDiffs balances |
258 | schema- block_number: uint32 |
259 | parquet | 260 |cryo geth_balance_diffs -b 10M:+100 |
261 |
geth stateDiffs codes |
264 | schema- block_number: uint32 |
265 | parquet | 266 |cryo geth_code_diffs -b 10M:+100 |
267 |
geth stateDiffs nonces |
270 | schema- block_number: uint32 |
271 | parquet | 272 |cryo geth_nonce_diffs -b 10M:+100 |
273 |
geth stateDiffs storages |
276 | schema- block_number: uint32 |
277 | parquet | 278 |cryo geth_storage_diffs -b 10M:+100 |
279 |
geth 4byte counts |
282 | schema- block_number: uint32 |
283 | parquet | 284 |cryo 4byte_counts -b 10M:+100 |
285 |