← previous blocknext block →recent activity

Analyzing

Block #107,806,101

18 transactions · 18 stateful · 2026-09-25 05:10:56 UTC

Parallelism

72/100

Blocked

39%

Avg conflicts / tx

0.72

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #107,806,101  ·  18 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

0xa1087a5c…66c4

0x754704…b603

10 touches
10 conflicts

0x2b54cadb…4425

0xd18b7e…414b

10 touches
10 conflicts

0xe89b3aed…cbd3

0x40c49f…2af0

8 touches
6 conflicts

0x6518075e…2b17

0x2a68ba…90c5

8 touches
6 conflicts

0x845ec8b0…c1af

0x34b655…2a6f

4 touches
1 conflict

0xba5743c7…21c6

0x1b6862…e19c

4 touches
1 conflict

0x3e6d4a39…5dfb

0x34b655…2a6f

4 touches
1 conflict

0x200b1692…9d50

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