← previous blocknext block →recent activity

Analyzing

Block #99,160,348

26 transactions · 21 stateful · 2026-08-25 22:20:05 UTC

Parallelism

92/100

Blocked

24%

Avg conflicts / tx

0.19

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #99,160,348  ·  26 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

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x01e7b865…6e6f

0x188d58…ea8e

4 touches
1 conflict

0x078e7aa7…992d

0x34b655…2a6f

4 touches
1 conflict

0x5ce19b50…f20f

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x92385428…6941

0x34b655…2a6f

4 touches
1 conflict

0xaba6578d…bd48

0x34b655…2a6f

4 touches
1 conflict

0xc10b903d…2f54

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 0x17606ba612…ea1b6e

← previous block·next block →recent activity