← previous blocknext block →recent activity
Analyzing
Block #87,059,291
14 transactions · 14 stateful · 2026-07-11 13:03:49 UTC
Parallelism
57/100
Blocked
43%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,059,291 · 14 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
2w03w17w18w29w310w411w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaa696d60…4266
0x34b655…2a6f
6 touches
3 conflicts
0x8dfef5ae…9361
0x34b655…2a6f
6 touches
3 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0xf9c7befd…e532
0x34b655…2a6f
6 touches
3 conflicts
0xf9c7befd…e533
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x8b87ece6…3353
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4ab
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 0xaa696d605c…1f4266
Audit this contract →
← previous block·next block →recent activity