← previous blocknext block →recent activity
Analyzing
Block #87,341,936
20 transactions · 16 stateful · 2026-07-12 20:33:50 UTC
Parallelism
75/100
Blocked
44%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,341,936 · 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
1w02w13w24w35w47w114w015w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x50d064c7…235a
0xd32edf…ff58
9 touches
10 conflicts
0xc6f1b3af…c97c
0x1001ff…1001
4 touches
1 conflict
0x00000000…0000
0x276664…5732
4 touches
1 conflict
0x00000000…0003
0x276664…5732
4 touches
1 conflict
0x00000000…0004
0x276664…5732
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xb4efdeeb…97f0
0x34b655…2a6f
4 touches
1 conflict
0xb815046f…4859
0x34b655…2a6f
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 0x50d064c7f7…9c235a
Audit this contract →
← previous block·next block →recent activity