← previous blocknext block →recent activity

Analyzing

Block #100,849,123

26 transactions · 22 stateful · 2026-08-31 20:17:17 UTC

Parallelism

77/100

Blocked

36%

Avg conflicts / tx

0.77

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #100,849,123  ·  26 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

12 touches
15 conflicts

0x2b54cadb…4425

0xd18b7e…414b

8 touches
6 conflicts

0xa3365f41…6bb7

0x40c49f…2af0

6 touches
3 conflicts

0x6518075e…2b17

0x2a68ba…90c5

6 touches
3 conflicts

0x6bf732ec…ae43

0xd32edf…ff58

5 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0xc61f3b52…caf6

0x065c9d…c394

4 touches
1 conflict

0xb87af72a…aef6

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)

15 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity