← previous blocknext block →recent activity

Analyzing

Block #95,808,573

17 transactions · 15 stateful · 2026-08-14 03:21:24 UTC

Parallelism

71/100

Blocked

47%

Avg conflicts / tx

0.65

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #95,808,573  ·  17 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

6 touches
3 conflicts

0x734ee320…caae

0x34b655…2a6f

6 touches
3 conflicts

0xe9452241…95a3

0x34b655…2a6f

6 touches
3 conflicts

0x054147bd…7a48

0x34b655…2a6f

4 touches
1 conflict

0xd55a7075…41b2

0x065c9d…c394

4 touches
1 conflict

0x002fed35…79fa

0x2a68ba…90c5

4 touches
1 conflict

0x1a5d321d…a474

0x34b655…2a6f

4 touches
1 conflict

0x3610cfd5…236a

0x34b655…2a6f

4 touches
1 conflict

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 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity