← previous blocknext block →recent activity

Analyzing

Block #94,970,583

22 transactions · 21 stateful · 2026-08-11 04:51:01 UTC

Parallelism

77/100

Blocked

38%

Avg conflicts / tx

0.77

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #94,970,583  ·  22 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x11258774…9892

0x2a68ba…90c5

6 touches
3 conflicts

0xec7d120d…7084

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x714ed46a…0525

0x065c9d…c394

6 touches
3 conflicts

0x581b829b…9578

0x34b655…2a6f

4 touches
1 conflict

0x6cd5cae5…1031

0x34b655…2a6f

4 touches
1 conflict

0x8ddcac26…5c5a

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