← previous blocknext block →recent activity

Analyzing

Block #89,711,411

17 transactions · 17 stateful · 2026-07-23 19:11:46 UTC

Parallelism

76/100

Blocked

41%

Avg conflicts / tx

0.65

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #89,711,411  ·  17 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

0x99c5409a…25b7

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x4f394483…ff62

0x34b655…2a6f

6 touches
3 conflicts

0x8218911e…3bed

0x34b655…2a6f

6 touches
3 conflicts

0x1e56f6b6…5940

0x34b655…2a6f

6 touches
3 conflicts

0xd7908b5f…56b9

0x34b655…2a6f

6 touches
3 conflicts

0xc77574e6…ec35

0xd32edf…ff58

5 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

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 0x99c5409a28…0025b7

← previous block·next block →recent activity