← previous blocknext block →recent activity
Analyzing
Block #87,724,260
27 transactions · 21 stateful · 2026-07-14 15:11:34 UTC
Parallelism
81/100
Blocked
48%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,724,260 · 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
1w02w17w28w39w010w114w015w118w419w221w124w325w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1dea6f2e…a7ce
0xd32edf…ff58
9 touches
10 conflicts
0x94ba9c4a…41d8
0x34b655…2a6f
8 touches
6 conflicts
0x8ae6d2fe…66f4
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x50e54461…beba
0x34b655…2a6f
4 touches
1 conflict
0x59991669…58c6
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x74500de0…8b2c
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 0x1dea6f2e1a…85a7ce
Audit this contract →
← previous block·next block →recent activity