← previous blocknext block →recent activity
Analyzing
Block #86,823,131
41 transactions · 37 stateful · 2026-07-10 10:45:28 UTC
Parallelism
73/100
Blocked
46%
Avg conflicts / tx
1.39
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #86,823,131 · 41 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w715w817w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2866c05a…750c
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xd35bb5ac…3586
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002b
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 0x2866c05a0b…f7750c
Audit this contract →
← previous block·next block →recent activity