← previous blocknext block →recent activity

Analyzing

Block #102,231,524

14 transactions · 14 stateful · 2026-09-05 16:25:20 UTC

Parallelism

86/100

Blocked

21%

Avg conflicts / tx

0.21

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #102,231,524  ·  14 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0xc52785b9…08f8

0x34b655…2a6f

4 touches
1 conflict

0xddf10453…d774

0x34b655…2a6f

4 touches
1 conflict

0xe6875750…9542

0x34b655…2a6f

4 touches
1 conflict

0xfcd7574f…a3a2

0x34b655…2a6f

4 touches
1 conflict

0xfd713bab…a651

0x34b655…2a6f

4 touches
1 conflict

0x4f3cc09a…2804

0x34b655…2a6f

4 touches
1 conflict

0x6c7c1a4b…5751

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)

1 conflict on slot 0xd17580f913…78ece1

← previous block·next block →recent activity