← previous blocknext block →recent activity
Analyzing
Block #100,852,217
33 transactions · 30 stateful · 2026-08-31 20:32:51 UTC
Parallelism
70/100
Blocked
70%
Avg conflicts / tx
1.61
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #100,852,217 · 33 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w421w522w430w631w732w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d9384dd…d198
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001b
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002b
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0xe5060fe3…ebe6
0x1b6862…e19c
8 touches
6 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: FastLane: FastLaneAuctionHandler
28 conflicts on slot 0x6d9384ddae…9bd198
Audit this contract →
← previous block·next block →recent activity