← previous blocknext block →recent activity

Analyzing

Block #91,406,320

23 transactions · 22 stateful · 2026-07-29 17:43:14 UTC

Parallelism

57/100

Blocked

50%

Avg conflicts / tx

1.35

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #91,406,320  ·  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

14 touches
21 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0x07d8b1e8…78c6

0x34b655…2a6f

6 touches
3 conflicts

0x3601aa45…29cb

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xbd6bf7ac…c102

0x34b655…2a6f

6 touches
3 conflicts

0x81561f70…fefd

0x34b655…2a6f

6 touches
3 conflicts

0x03aa8b26…118a

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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity