← previous blocknext block →recent activity

Analyzing

Block #102,741,542

17 transactions · 17 stateful · 2026-09-07 11:25:49 UTC

Parallelism

71/100

Blocked

47%

Avg conflicts / tx

0.94

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #102,741,542  ·  17 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

8 touches
6 conflicts

0xaad6be10…0801

0x2a68ba…90c5

8 touches
6 conflicts

0xfc75d69a…f15a

0x065c9d…c394

6 touches
3 conflicts

0x0778475b…bd75

0x2a68ba…90c5

6 touches
3 conflicts

0x8ffa3328…ce11

0xe52b14…7230

4 touches
1 conflict

0xf79df061…e005

0xe52b14…7230

4 touches
1 conflict

0x1a2055c7…9054

0x34b655…2a6f

4 touches
1 conflict

0x640c4fb2…044a

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