← previous blocknext block →recent activity
Analyzing
Block #86,281,793
31 transactions · 26 stateful · 2026-07-07 22:25:50 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
1.9
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #86,281,793 · 31 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w822w923w1025w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x297c151c…aa2d
0xd32edf…ff58
21 touches
55 conflicts
0xcc8faac2…c766
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
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
55 conflicts on slot 0x297c151c9b…4aaa2d
Audit this contract →
← previous block·next block →recent activity