← previous blocknext block →recent activity

Analyzing

Block #102,864,671

18 transactions · 17 stateful · 2026-09-07 21:48:32 UTC

Parallelism

67/100

Blocked

47%

Avg conflicts / tx

1.06

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #102,864,671  ·  18 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

12 touches
15 conflicts

0x331ef193…3bd2

0x34b655…2a6f

6 touches
3 conflicts

0x57070322…bc66

0xe52b14…7230

4 touches
1 conflict

0x8ffa3328…ce11

0xe52b14…7230

4 touches
1 conflict

0xf275b4ca…57b8

0xe52b14…7230

4 touches
1 conflict

0xf79df061…e005

0xe52b14…7230

4 touches
1 conflict

0x48ed1159…abe9

0x34ae4d…3fc5

2 touches
0 conflicts

0x0cc26bd6…acd6

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)

15 conflicts on slot 0xd17580f913…78ece1

← previous block·next block →recent activity