← previous blocknext block →recent activity
Analyzing
Block #89,772,311
7 transactions · 5 stateful · 2026-07-24 00:19:20 UTC
Parallelism
71/100
Blocked
20%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,772,311 · 7 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x2d1d07e4…eeda
0x34b655…2a6f
4 touches
1 conflict
0xfb53ecf8…bd11
0x34b655…2a6f
4 touches
1 conflict
0x00842ba8…bdc6
0x34b655…2a6f
2 touches
0 conflicts
0x10981d9e…6ebc
0x34b655…2a6f
2 touches
0 conflicts
0x2bb1123c…d9d1
0x34b655…2a6f
2 touches
0 conflicts
0x4cabb80a…46bf
0x34b655…2a6f
2 touches
0 conflicts
0x6d11d4a8…3a2d
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
1 conflict on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity