← previous blocknext block →recent activity

Analyzing

Block #105,377,626

18 transactions · 18 stateful · 2026-09-16 17:22:04 UTC

Parallelism

78/100

Blocked

44%

Avg conflicts / tx

0.67

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #105,377,626  ·  18 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0x1a979328…3f6a

0x34b655…2a6f

4 touches
1 conflict

0xf47b941b…b814

0xa6afd3…d132

4 touches
1 conflict

0x9abfeb11…cde8

0x34b655…2a6f

4 touches
1 conflict

0xfb9f065d…dd0d

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)

3 conflicts on slot 0xd17580f913…78ece1

← previous block·next block →recent activity