← previous blocknext block →recent activity

Analyzing

Block #94,372,422

19 transactions · 18 stateful · 2026-08-09 02:36:03 UTC

Parallelism

68/100

Blocked

50%

Avg conflicts / tx

0.79

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #94,372,422  ·  19 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

8 touches
6 conflicts

0x0778475b…bd75

0x2a68ba…90c5

6 touches
3 conflicts

0x002fed35…79fa

0x2a68ba…90c5

6 touches
3 conflicts

0xfa868baa…44f5

0x065c9d…c394

5 touches
3 conflicts

0x7bae29d5…64a6

0x065c9d…c394

5 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x34a1ee7e…fb20

0x34b655…2a6f

4 touches
1 conflict

0xbde524f4…43bf

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)

6 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity