← previous blocknext block →recent activity
Analyzing
Block #89,518,366
22 transactions · 20 stateful · 2026-07-22 23:10:53 UTC
Parallelism
68/100
Blocked
40%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #89,518,366 · 22 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
6w07w08w110w211w313w416w317w419w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xe068f0d8…ac71
0x34b655…2a6f
8 touches
6 conflicts
0xc6c7c954…80f3
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xd2274a53…9d6a
0x34b655…2a6f
6 touches
3 conflicts
0x78304d94…9e5e
0x34b655…2a6f
6 touches
3 conflicts
0x945bad58…cac3
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity