← previous blocknext block →recent activity
Analyzing
Block #86,233,116
24 transactions · 19 stateful · 2026-07-07 17:00:48 UTC
Parallelism
83/100
Blocked
26%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,233,116 · 24 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
1w02w13w26w012w313w014w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36c9f5a…26a4
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xdfa159d0…1576
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…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
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 0xc36c9f5a33…ea26a4
Audit this contract →
← previous block·next block →recent activity