← previous blocknext block →recent activity

Analyzing

Block #91,410,683

22 transactions · 20 stateful · 2026-07-29 18:05:21 UTC

Parallelism

73/100

Blocked

45%

Avg conflicts / tx

0.91

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #91,410,683  ·  22 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

0xebac0f82…a49c

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0000

0x019883…2a9a

8 touches
6 conflicts

0x00000000…0002

0x019883…2a9a

8 touches
6 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0003

0x019883…2a9a

8 touches
6 conflicts

0x99a3a7c1…1e2b

0x0cc9b2…7777

8 touches
6 conflicts

0xa472d565…9fe4

0x3bd359…433a

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

6 conflicts on slot 0xebac0f82ec…86a49c

← previous block·next block →recent activity