← previous blocknext block →recent activity
Analyzing
Block #89,555,212
19 transactions · 18 stateful · 2026-07-23 03:17:00 UTC
Parallelism
68/100
Blocked
44%
Avg conflicts / tx
1.11
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,555,212 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w16w28w310w411w013w416w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x67f87cdf…e5b6
0x34b655…2a6f
8 touches
6 conflicts
0x41a162d4…5091
0x34b655…2a6f
6 touches
3 conflicts
0x94ba9c4a…41d8
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x8ae6d2fe…66f4
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
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 0x67f87cdf50…cde5b6
Audit this contract →
← previous block·next block →recent activity