← previous blocknext block →recent activity

Analyzing

Block #107,795,453

27 transactions · 25 stateful · 2026-09-25 04:17:21 UTC

Parallelism

74/100

Blocked

40%

Avg conflicts / tx

1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #107,795,453  ·  27 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

12 touches
15 conflicts

0x2b54cadb…4425

0xd18b7e…414b

10 touches
10 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0x737acb78…fce8

0x34b655…2a6f

8 touches
6 conflicts

0x364b4cb5…cc92

0x40c49f…2af0

7 touches
6 conflicts

0x6518075e…2b17

0x2a68ba…90c5

7 touches
6 conflicts

0x002fed35…79fa

0x2a68ba…90c5

6 touches
3 conflicts

0x1f3809c1…f6ab

0x40c49f…2af0

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

15 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity