← previous blocknext block →recent activity

Analyzing

Block #90,947,225

22 transactions · 21 stateful · 2026-07-28 03:11:32 UTC

Parallelism

73/100

Blocked

43%

Avg conflicts / tx

0.86

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #90,947,225  ·  22 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

0xa0d3a786…91d9

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…00c9

0x34b655…2a6f

8 touches
6 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x1b1451d3…e1f4

0x34b655…2a6f

6 touches
3 conflicts

0x5c2230f4…9294

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…641f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…642d

0x34b655…2a6f

6 touches
3 conflicts

0xcdc1731c…b91a

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 0xa0d3a786de…b991d9

← previous block·next block →recent activity