← previous blocknext block →recent activity

Analyzing

Block #91,411,395

19 transactions · 16 stateful · 2026-07-29 18:08:58 UTC

Parallelism

79/100

Blocked

44%

Avg conflicts / tx

0.68

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #91,411,395  ·  19 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

0x5fad6fee…7714

0x34b655…2a6f

8 touches
6 conflicts

0x40ee7a94…d6a8

0x34b655…2a6f

8 touches
6 conflicts

0xd8deff1c…94e8

0x34b655…2a6f

8 touches
6 conflicts

0x84d6407e…6fb2

0x34b655…2a6f

8 touches
6 conflicts

0x542ff3d0…3fa7

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…641f

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…641e

0x34b655…2a6f

8 touches
6 conflicts

0x0733be30…112f

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 0x5fad6fee64…277714

← previous block·next block →recent activity