← previous blocknext block →recent activity
Analyzing
Block #86,851,864
25 transactions · 17 stateful · 2026-07-10 13:57:28 UTC
Parallelism
92/100
Blocked
24%
Avg conflicts / tx
0.24
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,851,864 · 25 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
1w05w06w07w09w111w112w013w122w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1eb0fab5…3517
0x34b655…2a6f
4 touches
1 conflict
0x2d94ecd9…43db
0x34b655…2a6f
4 touches
1 conflict
0x2ddad553…f810
0x34b655…2a6f
4 touches
1 conflict
0x2ddad553…f811
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x56f59993…2c32
0x34b655…2a6f
4 touches
1 conflict
0x6893debf…ca65
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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 0x1eb0fab556…473517
Audit this contract →
← previous block·next block →recent activity