← previous blocknext block →recent activity

Analyzing

Block #102,248,875

16 transactions · 16 stateful · 2026-09-05 17:53:18 UTC

Parallelism

56/100

Blocked

56%

Avg conflicts / tx

1.56

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #102,248,875  ·  16 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

0xd17580f9…ece1

0x754704…b603

14 touches
21 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x4188cc5f…2d2e

0x34b655…2a6f

4 touches
1 conflict

0xc636cc64…b14e

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xcb45d9d6…cb87

0x1b6862…e19c

2 touches
0 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

2 touches
0 conflicts

0x155e52ca…fac7

0x34b655…2a6f

2 touches
0 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)

21 conflicts on slot 0xd17580f913…78ece1

← previous block·next block →recent activity