← previous blocknext block →recent activity

Analyzing

Block #100,734,737

13 transactions · 11 stateful · 2026-08-31 10:41:27 UTC

Parallelism

85/100

Blocked

18%

Avg conflicts / tx

0.15

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #100,734,737  ·  13 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0xffc26b06…715f

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0036

0x35a73b…6042

4 touches
1 conflict

0xaf831072…51d5

0x69a5f9…2fef

4 touches
1 conflict

0xaf831072…51d6

0x69a5f9…2fef

4 touches
1 conflict

0xaf831072…51dc

0x69a5f9…2fef

4 touches
1 conflict

0x2ef1d89b…196d

0x754704…b603

4 touches
1 conflict

0x41e3f022…1f03

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)

1 conflict on slot 0xfda39b6f01…67d4cc

← previous block·next block →recent activity