← previous blocknext block →recent activity
Analyzing
Block #87,716,162
26 transactions · 23 stateful · 2026-07-14 14:17:22 UTC
Parallelism
77/100
Blocked
48%
Avg conflicts / tx
0.77
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,716,162 · 26 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
2w03w16w07w18w19w213w214w315w416w018w122w123w424w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa56e54d0…2d39
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xab5ba139…ea6f
0x34b655…2a6f
6 touches
3 conflicts
0x93b6fab0…09d6
0x34b655…2a6f
6 touches
3 conflicts
0x2965e2d6…5800
0x34b655…2a6f
4 touches
1 conflict
0x3095aa84…e9e3
0x34b655…2a6f
4 touches
1 conflict
0x4528594e…919a
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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
3 conflicts on slot 0xa56e54d018…f82d39
Audit this contract →
← previous block·next block →recent activity