← previous blocknext block →recent activity

Analyzing

Block #91,403,338

21 transactions · 19 stateful · 2026-07-29 17:28:07 UTC

Parallelism

43/100

Blocked

58%

Avg conflicts / tx

1.76

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #91,403,338  ·  21 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0x43fd3667…094b

0x34b655…2a6f

10 touches
10 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

10 touches
10 conflicts

0x468d132a…d7b8

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xa779293b…5e59

0x34b655…2a6f

8 touches
6 conflicts

0xbc66586e…20fe

0x34b655…2a6f

8 touches
6 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xab41643c…f9bf

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

10 conflicts on slot 0x43fd366775…d0094b

← previous block·next block →recent activity