← previous blocknext block →recent activity
Analyzing
Block #87,063,197
16 transactions · 16 stateful · 2026-07-11 13:29:51 UTC
Parallelism
81/100
Blocked
19%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,063,197 · 16 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
6w07w18w29w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa5ab7b8a…c97b
0x34b655…2a6f
6 touches
3 conflicts
0x8267cc91…78bc
0x34b655…2a6f
6 touches
3 conflicts
0x4bd41fd9…4194
0x34b655…2a6f
4 touches
1 conflict
0x56091b00…b694
0x34b655…2a6f
4 touches
1 conflict
0x687122ff…ced2
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x77f5ee28…347d
0x34b655…2a6f
4 touches
1 conflict
0x78d79dcd…a930
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 0xa5ab7b8a6d…b0c97b
Audit this contract →
← previous block·next block →recent activity