← previous blocknext block →recent activity
Analyzing
Block #100,134,980
20 transactions · 19 stateful · 2026-08-29 08:19:55 UTC
Parallelism
75/100
Blocked
37%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,134,980 · 20 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
1w02w13w24w06w39w310w412w014w115w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac135e6d…e4d4
0xd32edf…ff58
9 touches
10 conflicts
0x17a7f697…dcb6
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x2a07e64e…fe77
0x754704…b603
4 touches
1 conflict
0x00000000…0008
0x8964d7…10f8
4 touches
1 conflict
0x6f33ae13…77c1
0x8964d7…10f8
4 touches
1 conflict
0x6f33ae13…77c2
0x8964d7…10f8
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 0xac135e6df3…bce4d4
Audit this contract →
← previous block·next block →recent activity