← previous blocknext block →recent activity

Analyzing

Block #90,805,329

49 transactions · 40 stateful · 2026-07-27 15:17:36 UTC

Parallelism

75/100

Blocked

65%

Avg conflicts / tx

1.65

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #90,805,329  ·  49 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

16 touches
28 conflicts

0x66ba5e40…9cae

0xd32edf…ff58

13 touches
21 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x889d5e90…929a

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…002b

0x1b6862…e19c

6 touches
3 conflicts

0x794b8f81…3eaa

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x22e0cc1d…ad0d

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

28 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity