← previous blocknext block →recent activity
Analyzing
Block #88,353,755
16 transactions · 16 stateful · 2026-07-17 13:22:36 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.94
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #88,353,755 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w17w210w311w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0eac7709…66c3
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x5da59c2b…d7b2
0x34b655…2a6f
6 touches
3 conflicts
0x2a967872…3466
0x34b655…2a6f
6 touches
3 conflicts
0x388114fc…db6c
0x34b655…2a6f
6 touches
3 conflicts
0x388114fc…db6d
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
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 0x0eac770979…4766c3
Audit this contract →
← previous block·next block →recent activity