← previous blocknext block →recent activity

Analyzing

Block #91,273,905

22 transactions · 18 stateful · 2026-07-29 06:36:40 UTC

Parallelism

55/100

Blocked

67%

Avg conflicts / tx

1.64

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #91,273,905  ·  22 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x5502e1cc…3910

0x34b655…2a6f

8 touches
6 conflicts

0xebac0f82…a49c

0x34b655…2a6f

8 touches
6 conflicts

0xb9834665…e363

0x34b655…2a6f

8 touches
6 conflicts

0x9b86aa76…6f62

0x34b655…2a6f

8 touches
6 conflicts

0x0f69f34e…c78e

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x7aad02c6…b979

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity