← previous blocknext block →recent activity
Analyzing
Block #88,195,003
18 transactions · 16 stateful · 2026-07-16 19:41:10 UTC
Parallelism
72/100
Blocked
38%
Avg conflicts / tx
0.72
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #88,195,003 · 18 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
2w03w14w25w37w411w014w015w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee06e767…00d6
0x34b655…2a6f
8 touches
6 conflicts
0x3cb4b659…f735
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x734ee320…caae
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x88adad52…54b7
0x34b655…2a6f
6 touches
3 conflicts
0x07ed27ca…3903
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 0xee06e76704…0e00d6
Audit this contract →
← previous block·next block →recent activity