← previous blocknext block →recent activity
Analyzing
Block #86,816,534
23 transactions · 22 stateful · 2026-07-10 10:01:10 UTC
Parallelism
83/100
Blocked
50%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,816,534 · 23 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
1w02w13w25w18w09w110w212w313w014w115w017w118w219w322w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x90ab5afa…0aa1
0xd32edf…ff58
7 touches
6 conflicts
0xc7a15219…7745
0xa6afd3…d132
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x33bd5ec4…af53
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x56a919c4…ab49
0xee8c0e…1242
4 touches
1 conflict
0x729c91b8…9537
0x188d58…ea8e
4 touches
1 conflict
0x729c91b8…9539
0x188d58…ea8e
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 0x90ab5afa3e…e70aa1
Audit this contract →
← previous block·next block →recent activity