← previous blocknext block →recent activity

Analyzing

Block #91,151,509

23 transactions · 20 stateful · 2026-07-28 20:20:10 UTC

Parallelism

61/100

Blocked

50%

Avg conflicts / tx

0.91

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #91,151,509  ·  23 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

0xac2a0273…721b

0x34b655…2a6f

10 touches
10 conflicts

0x737acb78…fce8

0x34b655…2a6f

10 touches
10 conflicts

0xce06a0f7…efef

0x34b655…2a6f

8 touches
6 conflicts

0xbde524f4…43bf

0x34b655…2a6f

8 touches
6 conflicts

0xff8cb0b2…ab78

0x34b655…2a6f

7 touches
6 conflicts

0xb1d30b59…529f

0x34b655…2a6f

6 touches
3 conflicts

0xf51ec09c…b4a9

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

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 0xac2a02739b…81721b

← previous block·next block →recent activity