← previous blocknext block →recent activity

Analyzing

Block #107,613,253

22 transactions · 19 stateful · 2026-09-24 12:58:29 UTC

Parallelism

77/100

Blocked

32%

Avg conflicts / tx

0.77

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #107,613,253  ·  22 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

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xb409e204…89ac

0x34b655…2a6f

4 touches
1 conflict

0x50a294ea…9b01

0x34b655…2a6f

4 touches
1 conflict

0x4e638546…0894

0x34b655…2a6f

3 touches
1 conflict

0x06754f35…108d

0x34b655…2a6f

3 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)

10 conflicts on slot 0xd17580f913…78ece1

← previous block·next block →recent activity