← previous blocknext block →recent activity
Analyzing
Block #87,330,123
20 transactions · 17 stateful · 2026-07-12 19:14:50 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,330,123 · 20 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
1w06w09w110w213w015w316w418w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x567bb003…113a
0x34b655…2a6f
8 touches
6 conflicts
0xc0124edf…7d30
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x36890fff…f3d1
0x34b655…2a6f
6 touches
3 conflicts
0x63c900f4…2600
0x34b655…2a6f
4 touches
1 conflict
0x64aaadbf…f9f3
0x34b655…2a6f
4 touches
1 conflict
0x727fbce7…0c80
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 0x567bb0034c…9f113a
Audit this contract →
← previous block·next block →recent activity