← previous blocknext block →recent activity

Analyzing

Block #99,869,309

21 transactions · 20 stateful · 2026-08-28 10:01:53 UTC

Parallelism

81/100

Blocked

35%

Avg conflicts / tx

0.62

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #99,869,309  ·  21 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

8 touches
6 conflicts

0xb856d1a1…1f18

0x34b655…2a6f

6 touches
3 conflicts

0x16993363…919c

0x34b655…2a6f

6 touches
3 conflicts

0xe2d50773…c39e

0x34b655…2a6f

4 touches
1 conflict

0xfe65bb7b…12d7

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x54986533…78b2

0x34b655…2a6f

4 touches
1 conflict

0x62030a81…91be

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)

6 conflicts on slot 0xd17580f913…78ece1

← previous block·next block →recent activity