← previous blocknext block →recent activity
Analyzing
Block #86,281,179
20 transactions · 17 stateful · 2026-07-07 22:21:44 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,281,179 · 20 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
1w02w13w24w36w415w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b95c096…1e6e
0xd32edf…ff58
9 touches
10 conflicts
0x92d610a6…9a40
0x2a68ba…90c5
6 touches
3 conflicts
0xb89c7e78…0bec
0x1b6862…e19c
4 touches
1 conflict
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…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
10 conflicts on slot 0x2b95c096c3…a21e6e
Audit this contract →
← previous block·next block →recent activity