← previous blocknext block →recent activity

Analyzing

Block #89,865,724

23 transactions · 20 stateful · 2026-07-24 08:10:27 UTC

Parallelism

87/100

Blocked

30%

Avg conflicts / tx

0.35

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #89,865,724  ·  23 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xb33ff823…1188

0x065c9d…c394

4 touches
1 conflict

0x1041bcb3…4c7a

0x34b655…2a6f

4 touches
1 conflict

0x1baca9c3…2b23

0x34b655…2a6f

4 touches
1 conflict

0x217bd767…b79e

0x34b655…2a6f

4 touches
1 conflict

0x2b5101ac…090b

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 0xc824469a90…af6425

← previous block·next block →recent activity