← previous blocknext block →recent activity

Analyzing

Block #89,698,292

14 transactions · 14 stateful · 2026-07-23 18:05:40 UTC

Parallelism

71/100

Blocked

36%

Avg conflicts / tx

0.57

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #89,698,292  ·  14 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x8743e1ba…8331

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x89f9ad51…b082

0x0a2fbf…29b1

4 touches
1 conflict

0x89f9ad51…b085

0x0a2fbf…29b1

4 touches
1 conflict

0xc91796b2…1217

0x0a2fbf…29b1

4 touches
1 conflict

0xc91796b2…1218

0x0a2fbf…29b1

4 touches
1 conflict

0x2078c8e9…8a21

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

6 conflicts on slot 0x8743e1bab8…0a8331

← previous block·next block →recent activity