← previous blocknext block →recent activity

Analyzing

Block #91,151,507

13 transactions · 13 stateful · 2026-07-28 20:20:09 UTC

Parallelism

77/100

Blocked

46%

Avg conflicts / tx

0.69

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #91,151,507  ·  13 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x177211e2…1c2d

0x754704…b603

6 touches
3 conflicts

0xe1f61186…e2f8

0x754704…b603

6 touches
3 conflicts

0x00000000…0006

0x7b9256…1fb2

6 touches
3 conflicts

0x50e98724…fb4f

0x7b9256…1fb2

6 touches
3 conflicts

0x50e98724…fb50

0x7b9256…1fb2

6 touches
3 conflicts

0xff34eb7d…cc15

0x7b9256…1fb2

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x4bfdcd51…9b58

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: USDC (USDC)

3 conflicts on slot 0x177211e248…161c2d

← previous block·next block →recent activity