← previous blocknext block →recent activity

Analyzing

Block #98,664,859

24 transactions · 23 stateful · 2026-08-24 04:34:33 UTC

Parallelism

54/100

Blocked

57%

Avg conflicts / tx

2.08

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #98,664,859  ·  24 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

16 touches
28 conflicts

0x11b69a7e…334e

0xee8c0e…1242

14 touches
21 conflicts

0x002fed35…79fa

0x2a68ba…90c5

10 touches
10 conflicts

0xf48c4d36…1fdd

0xd32edf…ff58

9 touches
10 conflicts

0x57d02131…1fcc

0xa6afd3…d132

9 touches
10 conflicts

0x00000000…0028

0x1b6862…e19c

8 touches
6 conflicts

0x2bbc0cfb…c2bb

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

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)

28 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity