← previous blocknext block →recent activity
Analyzing
Block #86,301,560
35 transactions · 23 stateful · 2026-07-08 00:37:45 UTC
Parallelism
89/100
Blocked
43%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,301,560 · 35 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
1w02w13w24w19w010w119w321w223w325w326w333w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5ed07b9…3377
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0x8c42f949…c9d4
0x851145…3f07
6 touches
3 conflicts
0xcc8faac2…c766
0x065c9d…c394
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
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 0xc5ed07b9dc…1a3377
Audit this contract →
← previous block·next block →recent activity