← previous blocknext block →recent activity

Analyzing

Block #98,780,760

50 transactions · 39 stateful · 2026-08-24 14:23:25 UTC

Parallelism

80/100

Blocked

56%

Avg conflicts / tx

1.22

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #98,780,760  ·  50 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

0x00000000…003d

0xa6afd3…d132

14 touches
21 conflicts

0x03e5b578…2fec

0xa6afd3…d132

12 touches
15 conflicts

0x889d5e90…929a

0x2a68ba…90c5

12 touches
15 conflicts

0xf88ccd07…a684

0xa6afd3…d132

12 touches
15 conflicts

0xca841faa…486a

0x34b655…2a6f

10 touches
10 conflicts

0xb5c4826d…bdd6

0x2b46c0…1669

8 touches
6 conflicts

0xdb067026…9eb8

0x2b46c0…1669

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

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: Kuru Exchange: Market-WETH/USDC

21 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity