← previous blocknext block →recent activity
Analyzing
Block #89,749,080
15 transactions · 12 stateful · 2026-07-23 22:22:04 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,749,080 · 15 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
6w07w19w110w211w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x04e17b28…d9ef
0x34b655…2a6f
4 touches
1 conflict
0x04e17b28…d9f0
0x34b655…2a6f
4 touches
1 conflict
0x06ec4ccb…b190
0x34b655…2a6f
4 touches
1 conflict
0x264ddb78…fc48
0x34b655…2a6f
4 touches
1 conflict
0x43c15307…1175
0x34b655…2a6f
4 touches
1 conflict
0x53699236…fede
0x34b655…2a6f
4 touches
1 conflict
0x6719a767…9d62
0x34b655…2a6f
4 touches
1 conflict
0x71439842…8d3f
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
1 conflict on slot 0x04e17b28d0…ccd9ef
Audit this contract →
← previous block·next block →recent activity