← previous blocknext block →recent activity

Analyzing

Block #100,752,307

23 transactions · 20 stateful · 2026-08-31 12:09:50 UTC

Parallelism

70/100

Blocked

40%

Avg conflicts / tx

1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #100,752,307  ·  23 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

14 touches
21 conflicts

0x11b69a7e…334e

0x01bff4…1071

14 touches
21 conflicts

0x002fed35…79fa

0x2a68ba…90c5

8 touches
6 conflicts

0xa274bfbd…945f

0x851145…3f07

8 touches
6 conflicts

0x07b86c51…cdae

0x2a68ba…90c5

4 touches
1 conflict

0x4213f1c0…219a

0x2a68ba…90c5

4 touches
1 conflict

0x382434ca…96b5

0x34b655…2a6f

4 touches
1 conflict

0x81716ce9…095f

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)

21 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity