← previous blocknext block →recent activity

Analyzing

Block #94,968,756

17 transactions · 16 stateful · 2026-08-11 04:41:50 UTC

Parallelism

76/100

Blocked

38%

Avg conflicts / tx

0.71

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #94,968,756  ·  17 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

8 touches
6 conflicts

0x1a5d321d…a474

0x34b655…2a6f

6 touches
3 conflicts

0x603fba44…4155

0x34b655…2a6f

6 touches
3 conflicts

0x23ef1567…8f31

0x34b655…2a6f

4 touches
1 conflict

0x2652ac32…44f2

0x34b655…2a6f

4 touches
1 conflict

0x4a5956ef…e226

0x34b655…2a6f

4 touches
1 conflict

0x50887223…db7f

0x34b655…2a6f

4 touches
1 conflict

0x57330c5d…9973

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