← previous blocknext block →recent activity
Analyzing
Block #87,063,696
17 transactions · 16 stateful · 2026-07-11 13:33:11 UTC
Parallelism
53/100
Blocked
44%
Avg conflicts / tx
1.18
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,063,696 · 17 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w26w37w414w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x56b5f5c0…a3ad
0x34b655…2a6f
8 touches
6 conflicts
0x0842176f…86fa
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xb3e53c5e…b99c
0x34b655…2a6f
6 touches
3 conflicts
0xb4ab4257…11d7
0x34b655…2a6f
6 touches
3 conflicts
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
10 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity