← previous blocknext block →recent activity
Analyzing
Block #89,579,962
17 transactions · 15 stateful · 2026-07-23 06:02:17 UTC
Parallelism
65/100
Blocked
33%
Avg conflicts / tx
0.53
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,579,962 · 17 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
4w05w18w211w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x14c4e3ca…edda
0x34b655…2a6f
6 touches
3 conflicts
0x14c4e3ca…edd9
0x34b655…2a6f
6 touches
3 conflicts
0x2e19029d…72a7
0x34b655…2a6f
6 touches
3 conflicts
0x898d9b8a…d1ef
0x34b655…2a6f
4 touches
1 conflict
0xaf92ec04…4496
0x34b655…2a6f
4 touches
1 conflict
0xb0608dfe…083d
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity