← previous blocknext block →recent activity

Analyzing

Block #100,984,269

17 transactions · 17 stateful · 2026-09-01 07:37:04 UTC

Parallelism

71/100

Blocked

35%

Avg conflicts / tx

0.82

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #100,984,269  ·  17 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

0xd17580f9…ece1

0x754704…b603

10 touches
10 conflicts

0x93f1d5e2…9290

0x34b655…2a6f

4 touches
1 conflict

0xd9722304…6ed0

0x34b655…2a6f

4 touches
1 conflict

0x3ee8b564…4c49

0x34b655…2a6f

4 touches
1 conflict

0xe5bb3628…e5f1

0x34b655…2a6f

4 touches
1 conflict

0xeb88ed4e…a342

0x34b655…2a6f

4 touches
1 conflict

0xdab728fd…4b10

0x34b655…2a6f

4 touches
1 conflict

0x00000000…002e

0x1b6862…e19c

2 touches
0 conflicts

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 0xd17580f913…78ece1

← previous block·next block →recent activity