← previous blocknext block →recent activity
Analyzing
Block #86,964,559
11 transactions · 11 stateful · 2026-07-11 02:30:51 UTC
Parallelism
82/100
Blocked
9%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,964,559 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2f6d5b0a…2503
0xd32edf…ff58
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0fdbf0eb…373d
0x065c9d…c394
2 touches
0 conflicts
0x46d49a5b…a34e
0x065c9d…c394
2 touches
0 conflicts
0x6b78821a…c375
0x065c9d…c394
2 touches
0 conflicts
0x8b82d67f…d2b7
0x065c9d…c394
2 touches
0 conflicts
0x93ca4b3a…e5f1
0x065c9d…c394
2 touches
0 conflicts
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
1 conflict on slot 0x2f6d5b0a47…1d2503
Audit this contract →
← previous block·next block →recent activity