← previous blocknext block →recent activity

Analyzing

Block #102,231,685

16 transactions · 16 stateful · 2026-09-05 16:26:08 UTC

Parallelism

75/100

Blocked

44%

Avg conflicts / tx

0.63

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #102,231,685  ·  16 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x3a37aad1…720f

0x34b655…2a6f

4 touches
1 conflict

0x4f125e89…7ee0

0x34b655…2a6f

4 touches
1 conflict

0x71fad9ce…c11f

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x7c034520…a6b1

0x34b655…2a6f

4 touches
1 conflict

0x839c0c71…bada

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)

3 conflicts on slot 0xd17580f913…78ece1

← previous block·next block →recent activity