← previous blocknext block →recent activity
Analyzing
Block #87,714,099
14 transactions · 13 stateful · 2026-07-14 14:03:29 UTC
Parallelism
64/100
Blocked
31%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,714,099 · 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
7w08w19w210w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x5b6a7552…a4b8
0x34b655…2a6f
6 touches
3 conflicts
0xaec6ac00…1bd7
0x34b655…2a6f
6 touches
3 conflicts
0x5b6a7552…a4b9
0x34b655…2a6f
6 touches
3 conflicts
0x37cf3ee5…49e6
0x34b655…2a6f
4 touches
2 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x59991669…58c6
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
10 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity