← previous blocknext block →recent activity
Analyzing
Block #87,506,389
14 transactions · 14 stateful · 2026-07-13 14:53:40 UTC
Parallelism
57/100
Blocked
36%
Avg conflicts / tx
0.64
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,506,389 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w27w311w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x96bfa04d…d06b
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0xbbedfd60…0fec
0x34b655…2a6f
6 touches
3 conflicts
0x40b18770…e631
0x34b655…2a6f
6 touches
3 conflicts
0xfb9f51f4…0f16
0x34b655…2a6f
6 touches
3 conflicts
0x0b34a794…400b
0x34b655…2a6f
4 touches
1 conflict
0xd8b734c6…899d
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 0x96bfa04d52…3ed06b
Audit this contract →
← previous block·next block →recent activity