← previous blocknext block →recent activity
Analyzing
Block #87,287,394
21 transactions · 19 stateful · 2026-07-12 14:29:08 UTC
Parallelism
71/100
Blocked
37%
Avg conflicts / tx
0.48
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,287,394 · 21 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
1w03w16w07w18w010w212w113w318w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xacb691b6…8e39
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x98d58911…19f2
0x34b655…2a6f
4 touches
2 conflicts
0x2b43a4e4…1134
0x34b655…2a6f
4 touches
1 conflict
0x3fe71d84…9f53
0x34b655…2a6f
4 touches
1 conflict
0x727fbce7…0c80
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x74888025…a5b8
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 0xacb691b63c…a68e39
Audit this contract →
← previous block·next block →recent activity