← previous blocknext block →recent activity
Analyzing
Block #86,907,713
15 transactions · 14 stateful · 2026-07-10 20:11:01 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,907,713 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w07w18w19w212w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xae901867…8086
0x34b655…2a6f
4 touches
1 conflict
0xc70c02eb…7129
0x34b655…2a6f
4 touches
1 conflict
0xd5d88f31…0505
0x34b655…2a6f
4 touches
1 conflict
0xf31469a4…520d
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0xb06917e8…6985
0x34b655…2a6f
4 touches
1 conflict
0x3800d0ea…6168
0x34b655…2a6f
4 touches
1 conflict
0x3d4c0233…20a5
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
1 conflict on slot 0xae9018679a…898086
Audit this contract →
← previous block·next block →recent activity