← previous blocknext block →recent activity
Analyzing
Block #89,598,470
20 transactions · 19 stateful · 2026-07-23 08:05:53 UTC
Parallelism
75/100
Blocked
37%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,598,470 · 20 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
1w02w13w28w09w110w211w213w315w016w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e37574f…4145
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x582a39ab…45a1
0x34b655…2a6f
4 touches
1 conflict
0x719fada4…9950
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x95aab2d0…83a6
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
6 conflicts on slot 0x4e37574fae…ac4145
Audit this contract →
← previous block·next block →recent activity