← previous blocknext block →recent activity
Analyzing
Block #86,191,938
20 transactions · 18 stateful · 2026-07-07 12:25:47 UTC
Parallelism
80/100
Blocked
44%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,191,938 · 20 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
1w02w13w24w05w16w27w08w111w114w316w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdc1d99a0…6bd3
0xd32edf…ff58
7 touches
6 conflicts
0x47d4745e…02bb
0x336ed4…c59c
6 touches
3 conflicts
0xa779293b…5e59
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…000a
0x90c374…be45
6 touches
3 conflicts
0x00000000…000b
0x90c374…be45
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
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 0xdc1d99a067…826bd3
Audit this contract →
← previous block·next block →recent activity