← previous blocknext block →recent activity

Analyzing

Block #89,773,420

26 transactions · 24 stateful · 2026-07-24 00:24:58 UTC

Parallelism

58/100

Blocked

58%

Avg conflicts / tx

1.88

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #89,773,420  ·  26 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x734ee320…caae

0x34b655…2a6f

10 touches
10 conflicts

0xa3a621f8…75a2

0x34b655…2a6f

10 touches
10 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xe2e52e46…0894

0x34b655…2a6f

10 touches
10 conflicts

0x74f95963…01a2

0x34b655…2a6f

8 touches
6 conflicts

0x4cabb80a…46bf

0x34b655…2a6f

8 touches
6 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 0x734ee32053…cecaae

← previous block·next block →recent activity