← previous blocknext block →recent activity

Analyzing

Block #102,874,219

39 transactions · 35 stateful · 2026-09-07 22:36:35 UTC

Parallelism

77/100

Blocked

57%

Avg conflicts / tx

1.69

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #102,874,219  ·  39 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xd17580f9…ece1

0x754704…b603

18 touches
36 conflicts

0x66cca869…9087

0xd32edf…ff58

11 touches
15 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

10 touches
10 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x0a6cb118…4ca7

0x1b6862…e19c

6 touches
3 conflicts

0xf3d10975…0d07

0x34b655…2a6f

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

36 conflicts on slot 0xd17580f913…78ece1

← previous block·next block →recent activity