← previous blocknext block →recent activity
Analyzing
Block #87,901,585
13 transactions · 13 stateful · 2026-07-15 10:57:43 UTC
Parallelism
62/100
Blocked
54%
Avg conflicts / tx
0.92
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,901,585 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w26w07w28w39w411w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x76d36e11…fde2
0x34b655…2a6f
6 touches
3 conflicts
0x49f5a697…72c0
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xf5ea108a…dbf6
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x8eed7e30…c1ef
0x34b655…2a6f
4 touches
1 conflict
0x9f83113a…dcd8
0x34b655…2a6f
4 touches
1 conflict
0xa7ff65b9…8e90
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 0x76d36e11cd…6afde2
Audit this contract →
← previous block·next block →recent activity