← previous blocknext block →recent activity

Analyzing

Block #94,954,032

18 transactions · 18 stateful · 2026-08-11 03:27:47 UTC

Parallelism

78/100

Blocked

44%

Avg conflicts / tx

0.67

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #94,954,032  ·  18 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

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0x11258774…9892

0x2a68ba…90c5

4 touches
1 conflict

0x09e8ba87…1056

0x34b655…2a6f

4 touches
1 conflict

0x0db691ab…3ee3

0x34b655…2a6f

4 touches
1 conflict

0x424934c8…f2f1

0x34b655…2a6f

4 touches
1 conflict

0x45ea7a97…bbb3

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