← previous blocknext block →recent activity

Analyzing

Block #95,001,206

15 transactions · 13 stateful · 2026-08-11 07:25:01 UTC

Parallelism

80/100

Blocked

46%

Avg conflicts / tx

0.6

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #95,001,206  ·  15 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x00966e54…7d1d

0x34b655…2a6f

4 touches
1 conflict

0x19f95c80…eb21

0x34b655…2a6f

4 touches
1 conflict

0x50ec46ae…1c8a

0x34b655…2a6f

4 touches
1 conflict

0x64e5f38d…187c

0x34b655…2a6f

4 touches
1 conflict

0x6eb3e5af…064e

0x34b655…2a6f

4 touches
1 conflict

0x9a89094e…f5b2

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