← previous blocknext block →recent activity

Analyzing

Block #91,086,096

21 transactions · 20 stateful · 2026-07-28 14:51:03 UTC

Parallelism

57/100

Blocked

50%

Avg conflicts / tx

1.29

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #91,086,096  ·  21 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

0xbbeac3b7…c14b

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x49b8ccf1…2dd6

0x34b655…2a6f

6 touches
3 conflicts

0x4c619b7d…f4fa

0x34b655…2a6f

6 touches
3 conflicts

0x4ec9ff52…e6f7

0x34b655…2a6f

6 touches
3 conflicts

0x2ada3e8e…960f

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

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

15 conflicts on slot 0xbbeac3b703…d0c14b

← previous block·next block →recent activity