← previous blocknext block →recent activity

Analyzing

Block #102,744,021

17 transactions · 17 stateful · 2026-09-07 11:38:18 UTC

Parallelism

76/100

Blocked

47%

Avg conflicts / tx

0.71

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #102,744,021  ·  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

6 touches
3 conflicts

0xaad6be10…0801

0x2a68ba…90c5

6 touches
3 conflicts

0x0a2131b3…455e

0x34b655…2a6f

6 touches
3 conflicts

0x640c4fb2…044a

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…641d

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…641f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…642d

0x34b655…2a6f

6 touches
3 conflicts

0xd66696e0…0842

0x34b655…2a6f

6 touches
3 conflicts

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