← previous blocknext block →recent activity
Analyzing
Block #88,195,152
15 transactions · 15 stateful · 2026-07-16 19:42:10 UTC
Parallelism
73/100
Blocked
47%
Avg conflicts / tx
0.8
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #88,195,152 · 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
4w05w16w27w38w310w111w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x4ae1e116…4249
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x01154fff…c667
0x34b655…2a6f
6 touches
3 conflicts
0x7b59a70f…3818
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4a4
0x34b655…2a6f
6 touches
3 conflicts
0x84ff6484…363f
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity