← previous blocknext block →recent activity

Analyzing

Block #94,751,432

55 transactions · 33 stateful · 2026-08-10 10:28:26 UTC

Parallelism

85/100

Blocked

64%

Avg conflicts / tx

1.05

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #94,751,432  ·  55 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x9a555477…19a8

0x754704…b603

14 touches
21 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

14 touches
21 conflicts

0x00000000…0000

0x63e48b…53f2

14 touches
21 conflicts

0x00000000…0004

0x63e48b…53f2

14 touches
21 conflicts

0xb42eeb54…1730

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…0002

0x63e48b…53f2

12 touches
15 conflicts

0x391d170b…bd0f

0x3bd359…433a

10 touches
10 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 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)

21 conflicts on slot 0x9a55547719…9719a8

← previous block·next block →recent activity