← previous blocknext block →recent activity

Analyzing

Block #95,206,434

19 transactions · 18 stateful · 2026-08-12 00:38:10 UTC

Parallelism

68/100

Blocked

44%

Avg conflicts / tx

0.89

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #95,206,434  ·  19 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x2b54cadb…4425

0xd18b7e…414b

10 touches
10 conflicts

0x889d5e90…929a

0x2a68ba…90c5

8 touches
6 conflicts

0x45229dc1…f46c

0x40c49f…2af0

7 touches
6 conflicts

0x09e0690d…6e3d

0xe52b14…7230

4 touches
1 conflict

0x17bbe4f8…08c5

0xe52b14…7230

4 touches
1 conflict

0x3cebc8f1…975c

0xe52b14…7230

4 touches
1 conflict

0x58733c38…f2cd

0xe52b14…7230

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