← previous blocknext block →recent activity

Analyzing

Block #89,677,549

20 transactions · 20 stateful · 2026-07-23 16:21:02 UTC

Parallelism

55/100

Blocked

45%

Avg conflicts / tx

1.05

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #89,677,549  ·  20 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xc948dbdc…199a

0x34b655…2a6f

8 touches
6 conflicts

0xc6f3c5a3…3faa

0x34b655…2a6f

6 touches
3 conflicts

0x927ea5f9…e0c1

0x34b655…2a6f

6 touches
3 conflicts

0xb6ace8f5…3aab

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x725005f3…5b0e

0x34b655…2a6f

6 touches
3 conflicts

0xf1cc9519…84c1

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity