← previous blocknext block →recent activity
Analyzing
Block #86,447,323
28 transactions · 24 stateful · 2026-07-08 16:51:32 UTC
Parallelism
68/100
Blocked
63%
Avg conflicts / tx
1.36
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #86,447,323 · 28 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w710w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x954434c8…2a5c
0xd32edf…ff58
15 touches
28 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 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…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
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
28 conflicts on slot 0x954434c84e…de2a5c
Audit this contract →
← previous block·next block →recent activity