← previous blocknext block →recent activity
Analyzing
Block #87,489,724
22 transactions · 21 stateful · 2026-07-13 13:02:07 UTC
Parallelism
64/100
Blocked
48%
Avg conflicts / tx
1.41
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,489,724 · 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
1w02w16w07w18w211w113w214w315w416w517w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
16 touches
28 conflicts
0x0733be30…112f
0x34b655…2a6f
10 touches
10 conflicts
0x88adad52…54b7
0x34b655…2a6f
8 touches
6 conflicts
0x4c04ce68…d007
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0x3cb4b659…f735
0x34b655…2a6f
8 touches
6 conflicts
0xe9065ace…70fd
0x34b655…2a6f
6 touches
3 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
28 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity