← previous blocknext block →recent activity
Analyzing
Block #89,698,938
12 transactions · 11 stateful · 2026-07-23 18:08:55 UTC
Parallelism
50/100
Blocked
45%
Avg conflicts / tx
0.58
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,698,938 · 12 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
1w02w13w25w36w410w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda49f6b4…2482
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x7a2c83a3…a29a
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x310afe2c…83e1
0x34b655…2a6f
4 touches
1 conflict
0xfb4f6c11…7103
0x34b655…2a6f
4 touches
1 conflict
0x36890fff…f3d1
0x34b655…2a6f
2 touches
0 conflicts
0x41d7e149…baec
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0xda49f6b4aa…732482
Audit this contract →
← previous block·next block →recent activity