← previous blocknext block →recent activity

Analyzing

Block #102,741,565

19 transactions · 19 stateful · 2026-09-07 11:25:56 UTC

Parallelism

74/100

Blocked

37%

Avg conflicts / tx

0.79

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #102,741,565  ·  19 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

0xc1dcc246…2b22

0x065c9d…c394

10 touches
10 conflicts

0x0778475b…bd75

0x2a68ba…90c5

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x014e90b3…470f

0x34b655…2a6f

6 touches
3 conflicts

0x4bcbd0e7…5e26

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x4e4168ba…51c4

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