← previous blocknext block →recent activity

Analyzing

Block #98,734,321

23 transactions · 18 stateful · 2026-08-24 10:29:39 UTC

Parallelism

70/100

Blocked

50%

Avg conflicts / tx

0.7

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #98,734,321  ·  23 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x2b54cadb…4425

0xd18b7e…414b

10 touches
10 conflicts

0xa1087a5c…66c4

0x754704…b603

10 touches
10 conflicts

0x725bf924…2556

0x40c49f…2af0

8 touches
6 conflicts

0x6518075e…2b17

0x2a68ba…90c5

8 touches
6 conflicts

0x3a921be0…779c

0x2a68ba…90c5

6 touches
3 conflicts

0xc3d9b281…6231

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x5655f5c3…6b75

0x34b655…2a6f

4 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: Coinbase Wrapped BTC (cbBTC)

10 conflicts on slot 0x2b54cadb82…7c4425

← previous block·next block →recent activity