← previous blocknext block →recent activity
Analyzing
Block #86,714,202
51 transactions · 32 stateful · 2026-07-09 22:37:32 UTC
Parallelism
80/100
Blocked
66%
Avg conflicts / tx
1.12
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #86,714,202 · 51 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w26w37w48w59w610w738w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x50e1208f…0804
0xd32edf…ff58
17 touches
36 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xce827910…ff22
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0019
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
6 touches
3 conflicts
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
36 conflicts on slot 0x50e1208fa7…a40804
Audit this contract →
← previous block·next block →recent activity