← previous blocknext block →recent activity
Analyzing
Block #89,865,514
13 transactions · 11 stateful · 2026-07-24 08:09:24 UTC
Parallelism
54/100
Blocked
45%
Avg conflicts / tx
0.69
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,865,514 · 13 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
5w06w18w29w311w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x699d0a57…872f
0x34b655…2a6f
6 touches
3 conflicts
0x2b5101ac…090b
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x095a2c84…6648
0x34b655…2a6f
4 touches
1 conflict
0x374e3403…4546
0x34b655…2a6f
4 touches
1 conflict
0x4bb0bfb0…8f11
0x34b655…2a6f
4 touches
1 conflict
0x4ca2a6c3…ab80
0x34b655…2a6f
4 touches
1 conflict
0x72083f0d…082a
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 0x699d0a5763…ac872f
Audit this contract →
← previous block·next block →recent activity