← previous blocknext block →recent activity

Analyzing

Block #91,129,643

23 transactions · 21 stateful · 2026-07-28 18:30:09 UTC

Parallelism

57/100

Blocked

52%

Avg conflicts / tx

1.65

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #91,129,643  ·  23 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0xbc66586e…20fe

0x34b655…2a6f

10 touches
10 conflicts

0xc0eb79d1…29a4

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

8 touches
6 conflicts

0x0a370f34…31b9

0x34b655…2a6f

6 touches
3 conflicts

0x71b813c8…4a17

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity