← previous blocknext block →recent activity

Analyzing

Block #91,128,874

21 transactions · 20 stateful · 2026-07-28 18:26:17 UTC

Parallelism

48/100

Blocked

65%

Avg conflicts / tx

1.9

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #91,128,874  ·  21 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xc5c8022c…8d1f

0x34b655…2a6f

10 touches
10 conflicts

0xa779293b…5e59

0x34b655…2a6f

10 touches
10 conflicts

0xd676e291…3ecf

0x34b655…2a6f

10 touches
10 conflicts

0x206f4379…e08a

0x34b655…2a6f

8 touches
6 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0x40b02f96…4a15

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 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 0xc5c8022cb5…2c8d1f

← previous block·next block →recent activity