← previous blocknext block →recent activity

Analyzing

Block #90,796,022

25 transactions · 24 stateful · 2026-07-27 14:30:46 UTC

Parallelism

44/100

Blocked

63%

Avg conflicts / tx

1.88

Longest chain

14 deep

Execution timeline

did this block parallelize well?

view

block #90,796,022  ·  25 txs across 14 waves  ·  depth 14
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

wave w12

wave w13

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

14 touches
21 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

10 touches
10 conflicts

0x53f393fa…00b9

0x34b655…2a6f

6 touches
3 conflicts

0xcdc1731c…b91a

0x34b655…2a6f

6 touches
3 conflicts

0x41377979…0a18

0x34b655…2a6f

6 touches
3 conflicts

0x45f398c8…c1cb

0x34b655…2a6f

6 touches
3 conflicts

0x9fd372a1…a959

0x34b655…2a6f

6 touches
3 conflicts

0x34d95d94…3a16

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

← previous block·next block →recent activity