← previous blocknext block →recent activity

Analyzing

Block #91,272,627

22 transactions · 21 stateful · 2026-07-29 06:30:14 UTC

Parallelism

68/100

Blocked

43%

Avg conflicts / tx

0.77

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #91,272,627  ·  22 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

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x2fd12b6c…02cc

0x34b655…2a6f

6 touches
3 conflicts

0xebac0f82…a49c

0x34b655…2a6f

6 touches
3 conflicts

0xa0c570a0…7148

0x34b655…2a6f

6 touches
3 conflicts

0xfecb18c0…01ed

0x34b655…2a6f

6 touches
3 conflicts

0xfed09e59…a493

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…00c9

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

3 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity