← previous blocknext block →recent activity

Analyzing

Block #95,589,232

17 transactions · 14 stateful · 2026-08-13 08:57:08 UTC

Parallelism

82/100

Blocked

14%

Avg conflicts / tx

0.18

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #95,589,232  ·  17 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

0x521a5982…a82a

0x754704…b603

6 touches
3 conflicts

0x00000000…0006

0x968279…9342

6 touches
3 conflicts

0x177211e2…1c2d

0x754704…b603

4 touches
1 conflict

0xf8be0ab6…ca5a

0x968279…9342

4 touches
1 conflict

0xf8be0ab6…ca5b

0x968279…9342

3 touches
1 conflict

0x1e10796e…6214

0x34b655…2a6f

2 touches
0 conflicts

0x261cbea7…e35d

0x34b655…2a6f

2 touches
0 conflicts

0x261cbea7…e35e

0x34b655…2a6f

2 touches
0 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 0x521a5982b0…c2a82a

← previous block·next block →recent activity