← previous blocknext block →recent activity
Analyzing
Block #87,050,978
15 transactions · 14 stateful · 2026-07-11 12:08:15 UTC
Parallelism
73/100
Blocked
21%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,050,978 · 15 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
3w06w17w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda32dbe7…f6ee
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x001b7d74…69e0
0x34b655…2a6f
6 touches
3 conflicts
0x045c6c28…d296
0x34b655…2a6f
6 touches
3 conflicts
0x3389aed2…bde2
0x34b655…2a6f
6 touches
3 conflicts
0x5d3ae653…b43c
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4a4
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
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
3 conflicts on slot 0xda32dbe746…6df6ee
Audit this contract →
← previous block·next block →recent activity