← previous blocknext block →recent activity

Analyzing

Block #107,806,697

23 transactions · 22 stateful · 2026-09-25 05:13:56 UTC

Parallelism

70/100

Blocked

41%

Avg conflicts / tx

1.17

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #107,806,697  ·  23 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

14 touches
21 conflicts

0x2b54cadb…4425

0xd18b7e…414b

14 touches
21 conflicts

0x0b08bc22…9b71

0x40c49f…2af0

10 touches
10 conflicts

0x6518075e…2b17

0x2a68ba…90c5

9 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x0a85a226…83c1

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x6c5181e1…58f7

0xd32edf…ff58

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

21 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity