← previous blocknext block →recent activity

Analyzing

Block #94,050,263

20 transactions · 19 stateful · 2026-08-07 23:24:42 UTC

Parallelism

80/100

Blocked

37%

Avg conflicts / tx

0.45

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #94,050,263  ·  20 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

6 touches
3 conflicts

0x002fed35…79fa

0x2a68ba…90c5

4 touches
1 conflict

0xaec5efed…9874

0x065c9d…c394

4 touches
1 conflict

0x0778475b…bd75

0x2a68ba…90c5

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x6f2fecea…c969

0x34b655…2a6f

4 touches
1 conflict

0xa86351b8…2c5a

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