← previous blocknext block →recent activity

Analyzing

Block #100,740,976

24 transactions · 15 stateful · 2026-08-31 11:12:50 UTC

Parallelism

79/100

Blocked

53%

Avg conflicts / tx

0.58

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #100,740,976  ·  24 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

0x8f4d6173…166e

0x851145…3f07

8 touches
6 conflicts

0x11b69a7e…334e

0x01bff4…1071

8 touches
6 conflicts

0x07b86c51…cdae

0x2a68ba…90c5

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x261cbea7…e35d

0x34b655…2a6f

4 touches
1 conflict

0x261cbea7…e35e

0x34b655…2a6f

4 touches
1 conflict

0xcb187237…2559

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