← previous blocknext block →recent activity
Analyzing
Block #87,589,353
21 transactions · 18 stateful · 2026-07-14 00:09:16 UTC
Parallelism
62/100
Blocked
44%
Avg conflicts / tx
0.71
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,589,353 · 21 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
2w04w05w16w27w38w411w512w114w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x2af94348…eb23
0x34b655…2a6f
4 touches
1 conflict
0x2eac07de…595d
0x34b655…2a6f
4 touches
1 conflict
0x2fcaf77d…8bec
0x34b655…2a6f
4 touches
1 conflict
0x41ebf7ed…f662
0x34b655…2a6f
4 touches
1 conflict
0x4b628349…f327
0x34b655…2a6f
4 touches
1 conflict
0x640530ff…86bc
0x34b655…2a6f
4 touches
1 conflict
0x64687417…8d60
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity