← previous blocknext block →recent activity
Analyzing
Block #87,452,535
8 transactions · 6 stateful · 2026-07-13 08:53:27 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,452,535 · 8 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
8 touches
6 conflicts
0x4688dd30…ef52
0x34b655…2a6f
6 touches
3 conflicts
0x9354a4d0…be91
0x34b655…2a6f
4 touches
1 conflict
0xd9c52fc7…cbc1
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x1d84bebc…07d0
0x34b655…2a6f
4 touches
1 conflict
0x1d84bebc…07d1
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity