← previous blocknext block →recent activity
Analyzing
Block #87,879,294
25 transactions · 24 stateful · 2026-07-15 08:28:35 UTC
Parallelism
76/100
Blocked
38%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,879,294 · 25 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
1w05w06w18w29w311w113w414w517w018w119w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x255ba9f3…396d
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0x80fd3987…2314
0x34b655…2a6f
10 touches
10 conflicts
0x0733be30…112f
0x34b655…2a6f
10 touches
10 conflicts
0x147259c6…1709
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0000
0x019883…2a9a
8 touches
6 conflicts
0x00000000…0003
0x019883…2a9a
8 touches
6 conflicts
0x99a3a7c1…1e2b
0x0cc9b2…7777
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
15 conflicts on slot 0x255ba9f316…9a396d
Audit this contract →
← previous block·next block →recent activity