← previous blocknext block →recent activity

Analyzing

Block #98,656,004

32 transactions · 20 stateful · 2026-08-24 03:48:20 UTC

Parallelism

75/100

Blocked

50%

Avg conflicts / tx

0.84

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #98,656,004  ·  32 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

14 touches
21 conflicts

0x11b69a7e…334e

0xee8c0e…1242

12 touches
15 conflicts

0x889d5e90…929a

0x2a68ba…90c5

8 touches
6 conflicts

0x2a9e9bd1…5368

0x2a68ba…90c5

6 touches
3 conflicts

0x57895c9e…425f

0xa6afd3…d132

6 touches
3 conflicts

0x5261f6ab…9aa1

0xee8c0e…1242

4 touches
1 conflict

0x41755291…977f

0x065c9d…c394

4 touches
1 conflict

0xd6bd849a…5597

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)

21 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity