← previous blocknext block →recent activity
Analyzing
Block #87,621,587
16 transactions · 16 stateful · 2026-07-14 03:44:49 UTC
Parallelism
63/100
Blocked
38%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,621,587 · 16 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
1w02w04w05w18w29w110w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0x640530ff…86bc
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x36890fff…f3d1
0x34b655…2a6f
8 touches
6 conflicts
0x0f15f74f…8d72
0x34b655…2a6f
6 touches
3 conflicts
0x1737ef68…1e55
0x34b655…2a6f
6 touches
3 conflicts
0xf0ad9713…5796
0x34b655…2a6f
6 touches
3 conflicts
0x0f15f74f…8d71
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
15 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity