← previous blocknext block →recent activity

Analyzing

Block #91,088,287

20 transactions · 19 stateful · 2026-07-28 15:02:05 UTC

Parallelism

45/100

Blocked

58%

Avg conflicts / tx

1.7

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #91,088,287  ·  20 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

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xb4e0a934…5fc7

0x34b655…2a6f

6 touches
3 conflicts

0x4efae872…6aa8

0x34b655…2a6f

4 touches
1 conflict

0x5fe7e126…6dd2

0x34b655…2a6f

4 touches
1 conflict

0x66d5e476…8a1f

0x34b655…2a6f

4 touches
1 conflict

0x80398c66…f3cc

0x34b655…2a6f

4 touches
1 conflict

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