← previous blocknext block →recent activity
Analyzing
Block #100,920,466
27 transactions · 21 stateful · 2026-09-01 02:16:08 UTC
Parallelism
81/100
Blocked
57%
Avg conflicts / tx
0.89
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,920,466 · 27 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w08w111w212w113w114w116w217w318w320w423w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d744cc8…20a2
0xd32edf…ff58
9 touches
10 conflicts
0x6caf33e2…c261
0x34b655…2a6f
8 touches
6 conflicts
0xfd0635f7…0716
0x34b655…2a6f
8 touches
6 conflicts
0xe9a34da7…ddb7
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c4
0x1b6862…e19c
4 touches
1 conflict
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
10 conflicts on slot 0x2d744cc84d…f720a2
Audit this contract →
← previous block·next block →recent activity