← previous blocknext block →recent activity
Analyzing
Block #87,122,865
13 transactions · 11 stateful · 2026-07-11 20:08:20 UTC
Parallelism
69/100
Blocked
27%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,122,865 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w07w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdd38f4e6…586c
0x34b655…2a6f
8 touches
6 conflicts
0x98b248c3…9ea5
0x34b655…2a6f
8 touches
6 conflicts
0x619c81de…01b4
0x34b655…2a6f
8 touches
6 conflicts
0xdd38f4e6…586d
0x34b655…2a6f
6 touches
3 conflicts
0x008accc4…1da7
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x7ae44958…8593
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4ab
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
6 conflicts on slot 0xdd38f4e69f…fd586c
Audit this contract →
← previous block·next block →recent activity