← previous blocknext block →recent activity

Analyzing

Block #91,103,726

20 transactions · 19 stateful · 2026-07-28 16:19:47 UTC

Parallelism

65/100

Blocked

37%

Avg conflicts / tx

1.35

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #91,103,726  ·  20 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xbde524f4…43bf

0x34b655…2a6f

14 touches
21 conflicts

0xac2a0273…721b

0x34b655…2a6f

12 touches
15 conflicts

0x737acb78…fce8

0x34b655…2a6f

12 touches
15 conflicts

0xce06a0f7…efef

0x34b655…2a6f

12 touches
15 conflicts

0x6f0906cb…c7e5

0x34b655…2a6f

8 touches
6 conflicts

0x3d17d63a…35e7

0x34b655…2a6f

6 touches
3 conflicts

0x1404b00b…d8b3

0x34b655…2a6f

5 touches
3 conflicts

0x13df3104…acef

0x34b655…2a6f

5 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 0xbde524f475…b143bf

← previous block·next block →recent activity