← previous blocknext block →recent activity
Analyzing
Block #89,753,858
23 transactions · 18 stateful · 2026-07-23 22:46:12 UTC
Parallelism
78/100
Blocked
44%
Avg conflicts / tx
0.43
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,753,858 · 23 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
1w05w06w18w110w011w115w216w319w220w421w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x6c0af13b…b4c0
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0003
0x04ddf6…7f33
4 touches
1 conflict
0xaeabffea…5dd4
0x0a3323…0a3c
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x48e3acd8…cf41
0x34b655…2a6f
4 touches
1 conflict
0x59dccbd8…2bf6
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 0xf3d10975b0…050d07
Audit this contract →
← previous block·next block →recent activity