← previous blocknext block →recent activity
Analyzing
Block #87,513,318
15 transactions · 14 stateful · 2026-07-13 15:40:02 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.47
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,513,318 · 15 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
2w05w06w17w19w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc8f6f7a3…f563
0x34b655…2a6f
6 touches
3 conflicts
0xc8f6f7a3…f564
0x34b655…2a6f
6 touches
3 conflicts
0xdad3be8c…a703
0x34b655…2a6f
6 touches
3 conflicts
0x7c46fde6…d6a0
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xdc7f6181…432f
0x34b655…2a6f
4 touches
2 conflicts
0x69ce640b…884a
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4ab
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 0xc8f6f7a3f3…78f563
Audit this contract →
← previous block·next block →recent activity