← previous blocknext block →recent activity
Analyzing
Block #86,943,857
15 transactions · 11 stateful · 2026-07-11 00:12:30 UTC
Parallelism
80/100
Blocked
45%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,943,857 · 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
5w06w18w210w111w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0xf96f1cdc…d66e
0x34b655…2a6f
4 touches
1 conflict
0xedcf2991…8551
0x34b655…2a6f
4 touches
1 conflict
0xf83b23f9…5a2e
0x34b655…2a6f
4 touches
1 conflict
0xf83b23f9…5a2f
0x34b655…2a6f
4 touches
1 conflict
0x1191dbf7…8e85
0x34b655…2a6f
4 touches
1 conflict
0x3024d905…9fe3
0x34b655…2a6f
4 touches
1 conflict
0x4b9af402…c2d8
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
3 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity