← previous blocknext block →recent activity

Analyzing

Block #94,484,609

24 transactions · 21 stateful · 2026-08-09 12:05:11 UTC

Parallelism

63/100

Blocked

43%

Avg conflicts / tx

1.71

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #94,484,609  ·  24 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

18 touches
36 conflicts

0x002fed35…79fa

0x2a68ba…90c5

10 touches
10 conflicts

0x0778475b…bd75

0x2a68ba…90c5

10 touches
10 conflicts

0x5e337a8f…7321

0x065c9d…c394

10 touches
10 conflicts

0x43ab9d52…2513

0x065c9d…c394

10 touches
10 conflicts

0xa2478c84…6956

0x754704…b603

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x3040553c…5e28

0x754704…b603

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)

36 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity