← previous blocknext block →recent activity
Analyzing
Block #87,059,558
9 transactions · 7 stateful · 2026-07-11 13:05:35 UTC
Parallelism
67/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,059,558 · 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
3w04w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64d353bf…54ec
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x7840c762…8060
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x356f8a28…5791
0x34b655…2a6f
4 touches
1 conflict
0xc5decd02…dbf4
0x34b655…2a6f
4 touches
1 conflict
0x64d353bf…54eb
0x34b655…2a6f
4 touches
1 conflict
0x266a6b2c…4377
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
1 conflict on slot 0x64d353bf38…8f54ec
Audit this contract →
← previous block·next block →recent activity