← previous blocknext block →recent activity

Analyzing

Block #95,007,092

24 transactions · 18 stateful · 2026-08-11 07:54:39 UTC

Parallelism

83/100

Blocked

39%

Avg conflicts / tx

0.42

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #95,007,092  ·  24 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0x0778475b…bd75

0x2a68ba…90c5

4 touches
1 conflict

0x0d488000…3831

0x34b655…2a6f

4 touches
1 conflict

0xa3a621f8…75a2

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0xc7cf93d9…0fdd

0x065c9d…c394

4 touches
1 conflict

0x5a164ac1…4b9b

0x065c9d…c394

4 touches
1 conflict

0x002fed35…79fa

0x2a68ba…90c5

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)

6 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity