← previous blocknext block →recent activity
Analyzing
Block #89,377,161
17 transactions · 17 stateful · 2026-07-22 07:27:17 UTC
Parallelism
59/100
Blocked
41%
Avg conflicts / tx
1.35
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #89,377,161 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w39w410w512w613w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba059816…a847
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x451f6d31…81a8
0x34b655…2a6f
8 touches
6 conflicts
0x896db48d…380a
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x159cff26…7665
0x34b655…2a6f
6 touches
3 conflicts
0x5060cdde…445d
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
15 conflicts on slot 0xba0598166c…b0a847
Audit this contract →
← previous block·next block →recent activity