← previous blocknext block →recent activity
Analyzing
Block #87,585,152
22 transactions · 19 stateful · 2026-07-13 23:41:11 UTC
Parallelism
64/100
Blocked
58%
Avg conflicts / tx
1.41
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,585,152 · 22 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
1w03w04w15w26w39w410w411w512w613w115w720w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa562e808…4bde
0x34b655…2a6f
10 touches
10 conflicts
0xc80d6588…46bc
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x2b5101ac…090b
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0xcfddc3ab…e671
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
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
10 conflicts on slot 0xa562e808d0…1c4bde
Audit this contract →
← previous block·next block →recent activity