← previous blocknext block →recent activity

Analyzing

Block #100,231,135

14 transactions · 14 stateful · 2026-08-29 16:24:05 UTC

Parallelism

71/100

Blocked

57%

Avg conflicts / tx

0.93

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #100,231,135  ·  14 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

0x2ef1d89b…196d

0x754704…b603

8 touches
6 conflicts

0x00000000…0036

0x35a73b…6042

8 touches
6 conflicts

0xfda39b6f…d4cc

0x754704…b603

8 touches
6 conflicts

0xaf831072…51d5

0x69a5f9…2fef

8 touches
6 conflicts

0xaf831072…51d6

0x69a5f9…2fef

8 touches
6 conflicts

0xaf831072…51dc

0x69a5f9…2fef

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

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 0x2ef1d89b7e…45196d

← previous block·next block →recent activity