← previous blocknext block →recent activity

Analyzing

Block #95,194,826

19 transactions · 18 stateful · 2026-08-11 23:39:47 UTC

Parallelism

58/100

Blocked

56%

Avg conflicts / tx

1.79

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #95,194,826  ·  19 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

0xa1087a5c…66c4

0x754704…b603

16 touches
28 conflicts

0x2b54cadb…4425

0xd18b7e…414b

16 touches
28 conflicts

0x002fed35…79fa

0x2a68ba…90c5

8 touches
6 conflicts

0x34e7eeea…c36c

0x40c49f…2af0

8 touches
6 conflicts

0x6518075e…2b17

0x2a68ba…90c5

8 touches
6 conflicts

0xbde524f4…43bf

0x34b655…2a6f

8 touches
6 conflicts

0x12c536bd…98df

0x40c49f…2af0

8 touches
6 conflicts

0xac2a0273…721b

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)

28 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity