← previous blocknext block →recent activity

Analyzing

Block #90,822,498

22 transactions · 20 stateful · 2026-07-27 16:44:04 UTC

Parallelism

59/100

Blocked

55%

Avg conflicts / tx

1.45

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #90,822,498  ·  22 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

8 touches
6 conflicts

0xf50ebbf7…73c8

0x34b655…2a6f

8 touches
6 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0x80656e3b…9240

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xafe72ad3…c5fa

0x34b655…2a6f

8 touches
6 conflicts

0x74f95963…01a2

0x34b655…2a6f

6 touches
3 conflicts

0x0d488000…3831

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

6 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity