← previous blocknext block →recent activity

Analyzing

Block #100,924,038

22 transactions · 21 stateful · 2026-09-01 02:34:06 UTC

Parallelism

64/100

Blocked

43%

Avg conflicts / tx

1.09

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #100,924,038  ·  22 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xaad6be10…0801

0x2a68ba…90c5

10 touches
10 conflicts

0x002fed35…79fa

0x2a68ba…90c5

6 touches
3 conflicts

0x738202f6…ad06

0x065c9d…c394

6 touches
3 conflicts

0x5359bce1…be67

0x34b655…2a6f

4 touches
1 conflict

0x54c6fb44…369a

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x92385428…6941

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)

15 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity