← previous blocknext block →recent activity

Analyzing

Block #89,576,838

18 transactions · 16 stateful · 2026-07-23 05:41:27 UTC

Parallelism

67/100

Blocked

56%

Avg conflicts / tx

1.11

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #89,576,838  ·  18 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x21e273cb…b384

0x34b655…2a6f

8 touches
6 conflicts

0x9e70dadd…810e

0x34b655…2a6f

6 touches
3 conflicts

0x9e70dadd…810d

0x34b655…2a6f

6 touches
3 conflicts

0x91b0f8ed…6bd6

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x91b0f8ed…6bd7

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x8620c47a…99dc

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

6 conflicts on slot 0x21e273cb7e…3db384

← previous block·next block →recent activity