← previous blocknext block →recent activity
Analyzing
Block #87,506,434
14 transactions · 13 stateful · 2026-07-13 14:53:58 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,506,434 · 14 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
1w04w15w28w39w413w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0xfb9f51f4…0f16
0x34b655…2a6f
8 touches
6 conflicts
0xe8f5ee5e…bc54
0x34b655…2a6f
6 touches
3 conflicts
0x49ace3a1…e88c
0x34b655…2a6f
4 touches
1 conflict
0x50ca370b…22ad
0x34b655…2a6f
4 touches
1 conflict
0x595cbd16…dac4
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
6 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity