← previous blocknext block →recent activity

Analyzing

Block #90,919,065

21 transactions · 21 stateful · 2026-07-28 00:49:54 UTC

Parallelism

71/100

Blocked

43%

Avg conflicts / tx

0.9

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #90,919,065  ·  21 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

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0x23e8bf07…b834

0x34b655…2a6f

10 touches
10 conflicts

0x1cdfe548…d3aa

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x326a02b5…8dad

0x34b655…2a6f

6 touches
3 conflicts

0xe8eae8a3…bacc

0x34b655…2a6f

6 touches
3 conflicts

0xee8237bd…46ad

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

15 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity