← previous blocknext block →recent activity

Analyzing

Block #91,251,572

16 transactions · 15 stateful · 2026-07-29 04:43:34 UTC

Parallelism

56/100

Blocked

67%

Avg conflicts / tx

1.31

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #91,251,572  ·  16 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

0x6fe7d366…78ff

0x34b655…2a6f

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x28ceceef…ecc2

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x3b9bb58c…e73a

0x34b655…2a6f

6 touches
3 conflicts

0xfbe6a366…8ca1

0x34b655…2a6f

4 touches
1 conflict

0x0f2d78b1…7363

0x34b655…2a6f

4 touches
1 conflict

0x1d351a9b…f2dd

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

10 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity