← previous blocknext block →recent activity

Analyzing

Block #90,889,833

23 transactions · 22 stateful · 2026-07-27 22:22:49 UTC

Parallelism

57/100

Blocked

64%

Avg conflicts / tx

1.96

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #90,889,833  ·  23 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

0xc824469a…6425

0x34b655…2a6f

14 touches
21 conflicts

0x310afe2c…83e1

0x34b655…2a6f

12 touches
15 conflicts

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0x0bd95eb4…e562

0x34b655…2a6f

8 touches
6 conflicts

0xcdd32c46…e107

0x34b655…2a6f

8 touches
6 conflicts

0xd876b049…2927

0x34b655…2a6f

8 touches
6 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

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

21 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity