← previous blocknext block →recent activity
Analyzing
Block #89,544,200
19 transactions · 18 stateful · 2026-07-23 02:03:25 UTC
Parallelism
68/100
Blocked
44%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,544,200 · 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
3w04w16w07w18w09w210w311w412w114w517w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x8e3db883…fb9f
0x34b655…2a6f
6 touches
3 conflicts
0xb900efa2…8624
0x34b655…2a6f
6 touches
3 conflicts
0xc5dda21c…25f5
0x34b655…2a6f
6 touches
3 conflicts
0x8e914191…542d
0x34b655…2a6f
6 touches
3 conflicts
0x8e914191…542c
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
15 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity