← previous blocknext block →recent activity
Analyzing
Block #86,904,142
17 transactions · 14 stateful · 2026-07-10 19:47:06 UTC
Parallelism
65/100
Blocked
36%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,904,142 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w29w310w411w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92385428…6941
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x9d64d7f8…ce93
0x34b655…2a6f
6 touches
3 conflicts
0x03460269…9f96
0x34b655…2a6f
4 touches
1 conflict
0x0b320394…cc69
0x34b655…2a6f
4 touches
1 conflict
0xe3f11ed8…a8a6
0x34b655…2a6f
4 touches
1 conflict
0x01df0928…3426
0x34b655…2a6f
4 touches
1 conflict
0x01df0928…3427
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
15 conflicts on slot 0x92385428ad…dc6941
Audit this contract →
← previous block·next block →recent activity