← previous blocknext block →recent activity
Analyzing
Block #87,051,356
9 transactions · 9 stateful · 2026-07-11 12:10:45 UTC
Parallelism
67/100
Blocked
22%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,051,356 · 9 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x3b787279…727f
0x34b655…2a6f
4 touches
1 conflict
0x266a6b2c…4376
0x34b655…2a6f
2 touches
0 conflicts
0x266a6b2c…4377
0x34b655…2a6f
2 touches
0 conflicts
0x3312fcbd…c934
0x34b655…2a6f
2 touches
0 conflicts
0x3c39c2d4…8bd5
0x34b655…2a6f
2 touches
0 conflicts
0x4187b4dc…d465
0x34b655…2a6f
2 touches
0 conflicts
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity