← previous blocknext block →recent activity

Analyzing

Block #91,008,256

23 transactions · 18 stateful · 2026-07-28 08:19:15 UTC

Parallelism

83/100

Blocked

39%

Avg conflicts / tx

0.61

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #91,008,256  ·  23 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

0xc85f42b6…6f23

0x34b655…2a6f

8 touches
6 conflicts

0x442e26a3…e968

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x4e638546…0894

0x34b655…2a6f

4 touches
1 conflict

0x88fd7485…93c7

0x34b655…2a6f

4 touches
1 conflict

0x94e7f277…471b

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 0xc85f42b605…b36f23

← previous block·next block →recent activity