← previous blocknext block →recent activity
Analyzing
Block #89,758,708
12 transactions · 11 stateful · 2026-07-23 23:10:39 UTC
Parallelism
75/100
Blocked
45%
Avg conflicts / tx
0.75
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,758,708 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w17w28w210w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7fa88ae3…cf7c
0x34b655…2a6f
6 touches
3 conflicts
0x33967383…de4d
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x3e505a15…70f8
0x34b655…2a6f
4 touches
1 conflict
0x48e3acd8…cf41
0x34b655…2a6f
4 touches
1 conflict
0x4be9812b…48a9
0x34b655…2a6f
4 touches
1 conflict
0x57a52146…45f4
0x34b655…2a6f
4 touches
1 conflict
0x6c0e32fc…a6ca
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
3 conflicts on slot 0x7fa88ae3ba…7ecf7c
Audit this contract →
← previous block·next block →recent activity