← previous blocknext block →recent activity

Analyzing

Block #89,859,267

24 transactions · 19 stateful · 2026-07-24 07:37:58 UTC

Parallelism

63/100

Blocked

53%

Avg conflicts / tx

1.42

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #89,859,267  ·  24 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

0x734ee320…caae

0x34b655…2a6f

10 touches
10 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

10 touches
10 conflicts

0xd24005b3…645d

0x34b655…2a6f

8 touches
6 conflicts

0x43fd3667…094b

0x34b655…2a6f

6 touches
3 conflicts

0x66d5e476…8a1f

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x2840c278…bbc7

0x34b655…2a6f

6 touches
3 conflicts

0xb5a3b1be…8122

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

← previous block·next block →recent activity