← previous blocknext block →recent activity
Analyzing
Block #86,922,127
12 transactions · 11 stateful · 2026-07-10 21:47:17 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,922,127 · 12 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
1w02w13w04w16w07w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1ed670e…9e0b
0x34b655…2a6f
6 touches
3 conflicts
0x04105a34…6eea
0x34b655…2a6f
4 touches
1 conflict
0x157dbfb2…4089
0x34b655…2a6f
4 touches
1 conflict
0x2efac4f6…3abf
0x34b655…2a6f
4 touches
1 conflict
0x3ba014e3…35d5
0x34b655…2a6f
4 touches
1 conflict
0x3cd5188c…f3d2
0x34b655…2a6f
4 touches
1 conflict
0x3f23cdf6…46a4
0x34b655…2a6f
4 touches
1 conflict
0x5d7f309d…5145
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 0xe1ed670e1b…a39e0b
Audit this contract →
← previous block·next block →recent activity