← previous blocknext block →recent activity

Analyzing

Block #91,423,741

26 transactions · 19 stateful · 2026-07-29 19:11:07 UTC

Parallelism

85/100

Blocked

32%

Avg conflicts / tx

0.42

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #91,423,741  ·  26 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x0a3732b7…0939

0x34b655…2a6f

6 touches
3 conflicts

0x45255742…8386

0x34b655…2a6f

6 touches
3 conflicts

0x94f2c3b4…4ef6

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xd2e482cc…0a50

0x34b655…2a6f

6 touches
3 conflicts

0x5d913a50…0b0f

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity