← previous blocknext block →recent activity

Analyzing

Block #98,653,828

18 transactions · 18 stateful · 2026-08-24 03:36:53 UTC

Parallelism

67/100

Blocked

44%

Avg conflicts / tx

1.11

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #98,653,828  ·  18 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

12 touches
15 conflicts

0xb37cf90e…bb4c

0xa6afd3…d132

10 touches
10 conflicts

0x002fed35…79fa

0x2a68ba…90c5

10 touches
10 conflicts

0x11b69a7e…334e

0xee8c0e…1242

10 touches
10 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x0476d77b…a514

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x1a6414bb…a229

0x065c9d…c394

3 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)

15 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity