← previous blocknext block →recent activity
Analyzing
Block #86,447,408
30 transactions · 27 stateful · 2026-07-08 16:52:06 UTC
Parallelism
80/100
Blocked
37%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,447,408 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w49w012w115w020w121w422w527w028w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb2b6178a…f81d
0xd32edf…ff58
9 touches
10 conflicts
0x52e69143…95ad
0x065c9d…c394
6 touches
3 conflicts
0xfac61869…a55e
0x1b6862…e19c
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…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
10 conflicts on slot 0xb2b6178a54…3ef81d
Audit this contract →
← previous block·next block →recent activity