← previous blocknext block →recent activity

Analyzing

Block #90,571,976

19 transactions · 18 stateful · 2026-07-26 19:43:38 UTC

Parallelism

79/100

Blocked

44%

Avg conflicts / tx

0.63

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #90,571,976  ·  19 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0xe1f61186…e2f8

0x754704…b603

6 touches
3 conflicts

0x177211e2…1c2d

0x754704…b603

6 touches
3 conflicts

0x8dd53987…0cd9

0x7b9256…1fb2

5 touches
3 conflicts

0x8dd53987…0cda

0x7b9256…1fb2

5 touches
3 conflicts

0x8dd53987…0cdd

0x7b9256…1fb2

5 touches
3 conflicts

0x00000000…0006

0x7b9256…1fb2

5 touches
3 conflicts

0x316f4349…0493

0x7b9256…1fb2

5 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 0x6fe7d366be…a578ff

← previous block·next block →recent activity