← previous blocknext block →recent activity

Analyzing

Block #91,408,783

25 transactions · 19 stateful · 2026-07-29 17:55:43 UTC

Parallelism

64/100

Blocked

53%

Avg conflicts / tx

1.44

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #91,408,783  ·  25 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x6fe7d366…78ff

0x34b655…2a6f

12 touches
15 conflicts

0x1bf8d2af…d140

0x34b655…2a6f

8 touches
6 conflicts

0x6f8a6b52…6703

0x34b655…2a6f

8 touches
6 conflicts

0xc0eb79d1…29a4

0x34b655…2a6f

6 touches
3 conflicts

0xd676e291…3ecf

0x34b655…2a6f

6 touches
3 conflicts

0x4147b177…c9ba

0x34b655…2a6f

6 touches
3 conflicts

0x8eef368f…aa21

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

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

15 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity