← previous blocknext block →recent activity

Analyzing

Block #107,441,145

29 transactions · 28 stateful · 2026-09-23 22:31:57 UTC

Parallelism

66/100

Blocked

68%

Avg conflicts / tx

2.66

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #107,441,145  ·  29 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

20 touches
45 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0x00000000…001f

0x1b6862…e19c

8 touches
6 conflicts

0xcb45d9d6…cb87

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…00c9

0x34b655…2a6f

8 touches
6 conflicts

0xf0f95740…56e3

0xd32edf…ff58

7 touches
6 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

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

45 conflicts on slot 0xd17580f913…78ece1

← previous block·next block →recent activity