← previous blocknext block →recent activity

Analyzing

Block #90,797,330

18 transactions · 16 stateful · 2026-07-27 14:37:21 UTC

Parallelism

56/100

Blocked

56%

Avg conflicts / tx

1.22

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #90,797,330  ·  18 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

10 touches
10 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x9fd372a1…a959

0x34b655…2a6f

6 touches
3 conflicts

0x4f1ad4b4…e00a

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0x48cba2…b48b

4 touches
1 conflict

0x332ea34a…a4b6

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x5c16527f…628c

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

10 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity