← previous blocknext block →recent activity
Analyzing
Block #86,988,505
35 transactions · 25 stateful · 2026-07-11 05:10:49 UTC
Parallelism
89/100
Blocked
24%
Avg conflicts / tx
0.26
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,988,505 · 35 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w223w024w327w129w332w033w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb2997222…3e99
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x52e69143…95ad
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
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
6 conflicts on slot 0xb2997222f1…463e99
Audit this contract →
← previous block·next block →recent activity