← previous blocknext block →recent activity
Analyzing
Block #87,710,881
20 transactions · 19 stateful · 2026-07-14 13:41:55 UTC
Parallelism
60/100
Blocked
63%
Avg conflicts / tx
1.45
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,710,881 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w28w39w410w411w514w115w616w218w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x0dd44476…ef40
0x34b655…2a6f
6 touches
3 conflicts
0x4560e5a8…b741
0x34b655…2a6f
4 touches
1 conflict
0x50718952…7c75
0x34b655…2a6f
4 touches
1 conflict
0x5b8a1a43…4aea
0x34b655…2a6f
4 touches
1 conflict
0x64aaadbf…f9f3
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity