← previous blocknext block →recent activity
Analyzing
Block #87,713,730
24 transactions · 24 stateful · 2026-07-14 14:01:00 UTC
Parallelism
88/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,713,730 · 24 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
1w02w13w05w06w111w012w113w214w115w218w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x333c820d…10c1
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x07b02e84…2ff9
0xd32edf…ff58
5 touches
3 conflicts
0x5bb46f6c…7693
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x07d8b1e8…78c6
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad04
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 0x333c820d6f…7d10c1
Audit this contract →
← previous block·next block →recent activity