← previous blocknext block →recent activity
Analyzing
Block #87,729,872
16 transactions · 14 stateful · 2026-07-14 15:49:07 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,729,872 · 16 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
1w02w13w25w06w17w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b7950c1…2342
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xfa3848f5…98ee
0x34b655…2a6f
6 touches
3 conflicts
0xa9f59232…f58c
0x34b655…2a6f
6 touches
3 conflicts
0x85c84f98…06d7
0x34b655…2a6f
6 touches
3 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
6 touches
3 conflicts
0x8c0959b7…a4bf
0xd32edf…ff58
5 touches
3 conflicts
0x488cc9fc…d602
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 0x2b7950c182…352342
Audit this contract →
← previous block·next block →recent activity