← previous blocknext block →recent activity
Analyzing
Block #86,907,140
15 transactions · 14 stateful · 2026-07-10 20:07:11 UTC
Parallelism
53/100
Blocked
64%
Avg conflicts / tx
1.4
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,907,140 · 15 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w17w28w39w410w511w614w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x3800d0ea…6168
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x1941b441…5889
0x34b655…2a6f
6 touches
3 conflicts
0x6323c5ea…ce8a
0x34b655…2a6f
6 touches
3 conflicts
0xda6ebfcf…d51e
0x34b655…2a6f
6 touches
3 conflicts
0x8391fb68…4c83
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity