← previous blocknext block →recent activity
Analyzing
Block #86,786,530
25 transactions · 22 stateful · 2026-07-10 06:40:43 UTC
Parallelism
84/100
Blocked
27%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,786,530 · 25 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
1w02w04w05w16w27w08w116w017w018w119w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x303f16da…1076
0xd32edf…ff58
5 touches
3 conflicts
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…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0xd5b10148…e633
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
3 conflicts on slot 0x303f16da8b…3f1076
Audit this contract →
← previous block·next block →recent activity