← previous blocknext block →recent activity

Analyzing

Block #100,739,580

22 transactions · 21 stateful · 2026-08-31 11:05:49 UTC

Parallelism

68/100

Blocked

48%

Avg conflicts / tx

1.18

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #100,739,580  ·  22 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

10 touches
10 conflicts

0xd12f1d50…d601

0x851145…3f07

6 touches
3 conflicts

0x07b86c51…cdae

0x2a68ba…90c5

6 touches
3 conflicts

0xec27a071…d466

0xd32edf…ff58

5 touches
3 conflicts

0x002fed35…79fa

0x2a68ba…90c5

4 touches
1 conflict

0x038444a1…9b9f

0x065c9d…c394

4 touches
1 conflict

0xaad6be10…0801

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)

21 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity