← previous blocknext block →recent activity
Analyzing
Block #87,625,856
17 transactions · 16 stateful · 2026-07-14 04:13:23 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,625,856 · 17 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
3w04w15w06w210w311w412w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x326f2a00…a2a6
0x34b655…2a6f
6 touches
3 conflicts
0x5e51b8de…8d3a
0x34b655…2a6f
6 touches
3 conflicts
0x606df5d3…0960
0x34b655…2a6f
6 touches
3 conflicts
0x62cc9214…441b
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x41fc2b04…2805
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity