← previous blocknext block →recent activity

Analyzing

Block #98,738,076

31 transactions · 23 stateful · 2026-08-24 10:48:33 UTC

Parallelism

68/100

Blocked

48%

Avg conflicts / tx

1.13

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #98,738,076  ·  31 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x6c7f9e1f…e1e6

0x40c49f…2af0

10 touches
10 conflicts

0x2b54cadb…4425

0xd18b7e…414b

10 touches
10 conflicts

0x6518075e…2b17

0x2a68ba…90c5

10 touches
10 conflicts

0xe2d80784…8b73

0xd32edf…ff58

9 touches
10 conflicts

0x889d5e90…929a

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0xba5743c7…21c0

0x1b6862…e19c

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)

21 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity