← previous blocknext block →recent activity
Analyzing
Block #86,689,326
20 transactions · 19 stateful · 2026-07-09 19:51:34 UTC
Parallelism
80/100
Blocked
32%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,689,326 · 20 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
4w05w06w111w212w316w017w118w219w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0xfe2b47…c052
4 touches
1 conflict
0x461428a9…24b3
0x34b655…2a6f
4 touches
1 conflict
0x469e26f1…62ec
0x34b655…2a6f
4 touches
1 conflict
0x4967209f…faa7
0x34b655…2a6f
4 touches
1 conflict
0x93701943…012b
0x34b655…2a6f
4 touches
1 conflict
0xc5decd02…dbf4
0x34b655…2a6f
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: Perpl
6 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity