← previous blocknext block →recent activity

Analyzing

Block #90,809,940

22 transactions · 21 stateful · 2026-07-27 15:40:50 UTC

Parallelism

50/100

Blocked

52%

Avg conflicts / tx

1.64

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #90,809,940  ·  22 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

12 touches
15 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0x309b5194…0017

0x34b655…2a6f

8 touches
6 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0x326a02b5…8dad

0x34b655…2a6f

8 touches
6 conflicts

0xa45116ed…5331

0x34b655…2a6f

8 touches
6 conflicts

0x344bc09a…942f

0x34b655…2a6f

8 touches
6 conflicts

0xe8d8a9a2…40f3

0x34b655…2a6f

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity