← previous blocknext block →recent activity
Analyzing
Block #87,628,159
17 transactions · 13 stateful · 2026-07-14 04:28:49 UTC
Parallelism
71/100
Blocked
54%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,628,159 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w26w27w38w49w010w115w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef1cbbb7…8cc8
0x34b655…2a6f
8 touches
6 conflicts
0x11d629eb…bcd9
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x3f0792d7…4742
0x34b655…2a6f
4 touches
1 conflict
0x56f7eb8f…b837
0x34b655…2a6f
4 touches
1 conflict
0x5b6a7552…a4b8
0x34b655…2a6f
4 touches
1 conflict
0x5b6a7552…a4b9
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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
6 conflicts on slot 0xef1cbbb7ac…328cc8
Audit this contract →
← previous block·next block →recent activity