← previous blocknext block →recent activity
Analyzing
Block #89,377,155
15 transactions · 13 stateful · 2026-07-22 07:27:14 UTC
Parallelism
67/100
Blocked
46%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,377,155 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w16w27w110w111w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x896db48d…380a
0x34b655…2a6f
6 touches
3 conflicts
0xba059816…a847
0x34b655…2a6f
6 touches
3 conflicts
0x24c39dc5…9add
0x34b655…2a6f
4 touches
1 conflict
0x2546c113…3198
0x34b655…2a6f
4 touches
1 conflict
0x301e1c77…9e30
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x48b13e5e…3c2a
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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 0x896db48d73…de380a
Audit this contract →
← previous block·next block →recent activity