← previous blocknext block →recent activity

Analyzing

Block #94,913,507

24 transactions · 20 stateful · 2026-08-11 00:03:56 UTC

Parallelism

79/100

Blocked

40%

Avg conflicts / tx

0.75

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #94,913,507  ·  24 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

10 touches
10 conflicts

0xaf02d49b…be75

0xd32edf…ff58

7 touches
6 conflicts

0x11b69a7e…334e

0x01bff4…1071

6 touches
3 conflicts

0x002fed35…79fa

0x2a68ba…90c5

6 touches
3 conflicts

0xa8e98b9f…5935

0x01bff4…1071

4 touches
1 conflict

0x524f0872…0d12

0x34b655…2a6f

4 touches
1 conflict

0x734ee320…caae

0x34b655…2a6f

4 touches
1 conflict

0x7deb183c…0858

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)

10 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity