← previous blocknext block →recent activity

Analyzing

Block #89,773,611

16 transactions · 15 stateful · 2026-07-24 00:25:56 UTC

Parallelism

56/100

Blocked

67%

Avg conflicts / tx

1.5

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #89,773,611  ·  16 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x6fe7d366…78ff

0x34b655…2a6f

12 touches
15 conflicts

0xba1edffb…323e

0x34b655…2a6f

8 touches
6 conflicts

0x2ec3ce57…0773

0x34b655…2a6f

6 touches
3 conflicts

0x7265fa19…9534

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…00c9

0x34b655…2a6f

6 touches
3 conflicts

0x99c5409a…25b7

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

15 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity