← previous blocknext block →recent activity

Analyzing

Block #90,801,578

24 transactions · 22 stateful · 2026-07-27 14:58:44 UTC

Parallelism

75/100

Blocked

32%

Avg conflicts / tx

0.71

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #90,801,578  ·  24 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xabd0bcfc…64e2

0x34b655…2a6f

6 touches
3 conflicts

0x17b720f5…ad7a

0x34b655…2a6f

6 touches
3 conflicts

0x45ef9175…5ab2

0x34b655…2a6f

6 touches
3 conflicts

0x53f393fa…00b9

0x34b655…2a6f

6 touches
3 conflicts

0x4c700390…ce3b

0x34b655…2a6f

6 touches
3 conflicts

0xa3f6f7c8…2436

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 0x482471adbb…39122f

← previous block·next block →recent activity