← previous blocknext block →recent activity
Analyzing
Block #86,389,179
33 transactions · 26 stateful · 2026-07-08 10:23:12 UTC
Parallelism
85/100
Blocked
42%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,389,179 · 33 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w210w211w012w114w015w116w020w324w426w427w130w131w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7180ab11…ce69
0xd32edf…ff58
9 touches
10 conflicts
0x49cbdb1b…bda4
0x065c9d…c394
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…001a
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
6 touches
3 conflicts
0x261261a7…6170
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 0x7180ab1199…66ce69
Audit this contract →
← previous block·next block →recent activity