← previous blocknext block →recent activity

Analyzing

Block #107,806,886

20 transactions · 19 stateful · 2026-09-25 05:14:53 UTC

Parallelism

70/100

Blocked

42%

Avg conflicts / tx

0.95

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #107,806,886  ·  20 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

10 touches
10 conflicts

0x2b54cadb…4425

0xd18b7e…414b

10 touches
10 conflicts

0x002fed35…79fa

0x2a68ba…90c5

8 touches
6 conflicts

0xc806e70f…a36f

0x40c49f…2af0

7 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x6518075e…2b17

0x2a68ba…90c5

6 touches
3 conflicts

0xdb9404dc…ae5a

0x40c49f…2af0

5 touches
3 conflicts

0x9fcf8df5…88c7

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)

10 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity