← previous blocknext block →recent activity

Analyzing

Block #99,171,840

17 transactions · 17 stateful · 2026-08-25 23:17:53 UTC

Parallelism

71/100

Blocked

53%

Avg conflicts / tx

0.94

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #99,171,840  ·  17 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0x889d5e90…929a

0x2a68ba…90c5

8 touches
6 conflicts

0x41c56387…a8f6

0x34b655…2a6f

6 touches
3 conflicts

0xef449589…92a1

0x34b655…2a6f

6 touches
3 conflicts

0x02e9036e…3948

0x065c9d…c394

5 touches
3 conflicts

0x00e21a9f…3583

0x34b655…2a6f

4 touches
1 conflict

0x0f8965bb…e238

0x34b655…2a6f

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

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 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity