← previous blocknext block →recent activity

Analyzing

Block #98,752,407

17 transactions · 15 stateful · 2026-08-24 12:00:40 UTC

Parallelism

65/100

Blocked

53%

Avg conflicts / tx

0.76

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #98,752,407  ·  17 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

8 touches
6 conflicts

0x2b54cadb…4425

0xd18b7e…414b

8 touches
6 conflicts

0xe1c4e5ce…0dec

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xbd590df7…9891

0x34b655…2a6f

6 touches
3 conflicts

0x3a921be0…779c

0x2a68ba…90c5

6 touches
3 conflicts

0x6518075e…2b17

0x2a68ba…90c5

6 touches
3 conflicts

0x8b780b26…f5ff

0x34b655…2a6f

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

6 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity