← previous blocknext block →recent activity

Analyzing

Block #91,445,996

20 transactions · 19 stateful · 2026-07-29 21:03:55 UTC

Parallelism

75/100

Blocked

42%

Avg conflicts / tx

0.95

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #91,445,996  ·  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

0x80dd8064…1ea1

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0x31684331…a008

0x34b655…2a6f

4 touches
1 conflict

0x4acc6dca…a868

0x34b655…2a6f

4 touches
1 conflict

0x4c619b7d…f4fa

0x34b655…2a6f

4 touches
1 conflict

0x620b761c…270e

0x34b655…2a6f

4 touches
1 conflict

0x65487580…b5eb

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

10 conflicts on slot 0x80dd806471…351ea1

← previous block·next block →recent activity