← previous blocknext block →recent activity

Analyzing

Block #100,853,149

19 transactions · 19 stateful · 2026-08-31 20:37:32 UTC

Parallelism

74/100

Blocked

42%

Avg conflicts / tx

0.79

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #100,853,149  ·  19 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

10 touches
10 conflicts

0x2b54cadb…4425

0xd18b7e…414b

10 touches
10 conflicts

0xac7262db…20a9

0x40c49f…2af0

6 touches
3 conflicts

0x2202504e…fad0

0x34b655…2a6f

6 touches
3 conflicts

0x002fed35…79fa

0x2a68ba…90c5

6 touches
3 conflicts

0x326a02b5…8dad

0x34b655…2a6f

4 touches
1 conflict

0x3e1e8e54…9c83

0x2a68ba…90c5

4 touches
1 conflict

0x7ce74eed…3383

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)

10 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity