← previous blocknext block →recent activity

Analyzing

Block #91,074,022

20 transactions · 19 stateful · 2026-07-28 13:50:15 UTC

Parallelism

75/100

Blocked

37%

Avg conflicts / tx

0.7

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #91,074,022  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x38b5b2ce…c5bb

0xfa32f9…f3f0

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0x99f666e3…b2a2

0x3bd359…433a

6 touches
3 conflicts

0x9194f4a3…10b8

0x754704…b603

6 touches
3 conflicts

0x00000000…0000

0xfa32f9…f3f0

6 touches
3 conflicts

0x00000000…0001

0xfa32f9…f3f0

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

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 0xc824469a90…af6425

← previous block·next block →recent activity