← previous blocknext block →recent activity

Analyzing

Block #102,801,718

18 transactions · 18 stateful · 2026-09-07 16:31:38 UTC

Parallelism

72/100

Blocked

33%

Avg conflicts / tx

0.89

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #102,801,718  ·  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

0x85852a31…c36a

0x40c49f…2af0

10 touches
10 conflicts

0x2b54cadb…4425

0xd18b7e…414b

10 touches
10 conflicts

0x6518075e…2b17

0x2a68ba…90c5

9 touches
10 conflicts

0xf1231bea…990b

0x34b655…2a6f

6 touches
3 conflicts

0x55010ec8…ea31

0x34b655…2a6f

4 touches
1 conflict

0xaa512b2b…6a84

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

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