← previous blocknext block →recent activity

Analyzing

Block #95,854,841

18 transactions · 18 stateful · 2026-08-14 07:14:09 UTC

Parallelism

67/100

Blocked

50%

Avg conflicts / tx

1.06

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #95,854,841  ·  18 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

12 touches
15 conflicts

0x34986892…56fb

0x065c9d…c394

10 touches
10 conflicts

0x0778475b…bd75

0x2a68ba…90c5

10 touches
10 conflicts

0x0d488000…3831

0x34b655…2a6f

4 touches
1 conflict

0xa8e0d14e…c6b4

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0xd16c07ff…1e55

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

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)

15 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity