← previous blocknext block →recent activity
Analyzing
Block #86,237,863
28 transactions · 24 stateful · 2026-07-07 17:32:28 UTC
Parallelism
82/100
Blocked
46%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,237,863 · 28 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
1w02w13w24w35w07w18w09w110w214w015w118w419w121w424w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe38c722f…2a38
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0002
0x04fdea…47d7
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0xab2a87f1…eb02
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
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 0xe38c722f99…c62a38
Audit this contract →
← previous block·next block →recent activity