← previous blocknext block →recent activity
Analyzing
Block #89,406,305
13 transactions · 11 stateful · 2026-07-22 10:42:10 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,406,305 · 13 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
3w05w16w211w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x091164f5…6e33
0x34b655…2a6f
6 touches
3 conflicts
0x9f4bc324…e6a6
0x34b655…2a6f
6 touches
3 conflicts
0x091164f5…6e32
0x34b655…2a6f
6 touches
3 conflicts
0x1951ee47…540f
0x34b655…2a6f
4 touches
1 conflict
0x24f05489…caf9
0x34b655…2a6f
4 touches
1 conflict
0x2b7950c1…2342
0x34b655…2a6f
4 touches
1 conflict
0x37773728…f3a4
0x34b655…2a6f
4 touches
1 conflict
0x39bd1fab…a39c
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 0x091164f59d…fd6e33
Audit this contract →
← previous block·next block →recent activity