← previous blocknext block →recent activity
Analyzing
Block #87,577,328
20 transactions · 17 stateful · 2026-07-13 22:48:51 UTC
Parallelism
85/100
Blocked
29%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,577,328 · 20 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
1w03w15w06w19w010w011w112w218w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2607c11…8fa7
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x48e6f054…d2ac
0x34b655…2a6f
4 touches
1 conflict
0x56f53fc9…46c2
0x34b655…2a6f
4 touches
1 conflict
0x6fa48528…fdbd
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0xe2607c113c…068fa7
Audit this contract →
← previous block·next block →recent activity