← previous blocknext block →recent activity

Analyzing

Block #91,905,766

6 transactions · 6 stateful · 2026-07-31 11:36:56 UTC

Parallelism

67/100

Blocked

33%

Avg conflicts / tx

0.33

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #91,905,766  ·  6 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x4d4389b2…6e07

0x34b655…2a6f

4 touches
1 conflict

0xab41643c…f9bf

0x34b655…2a6f

4 touches
1 conflict

0xb9b077a8…e029

0x34b655…2a6f

4 touches
1 conflict

0xc3baa205…f26e

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xef79589c…0088

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

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

1 conflict on slot 0x4d4389b20d…b56e07

← previous block·next block →recent activity