← previous blocknext block →recent activity

Analyzing

Block #100,230,199

21 transactions · 19 stateful · 2026-08-29 16:19:23 UTC

Parallelism

86/100

Blocked

32%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #100,230,199  ·  21 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

0xfda39b6f…d4cc

0x754704…b603

6 touches
3 conflicts

0x8ec95f2b…f4d7

0x34b655…2a6f

6 touches
3 conflicts

0xab981df1…2941

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0036

0x35a73b…6042

6 touches
3 conflicts

0xaf831072…51d5

0x69a5f9…2fef

6 touches
3 conflicts

0xaf831072…51d6

0x69a5f9…2fef

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 0xfda39b6f01…67d4cc

← previous block·next block →recent activity