← previous blocknext block →recent activity

Analyzing

Block #98,724,228

19 transactions · 19 stateful · 2026-08-24 09:38:54 UTC

Parallelism

68/100

Blocked

47%

Avg conflicts / tx

1.11

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #98,724,228  ·  19 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

0x2b54cadb…4425

0xd18b7e…414b

10 touches
10 conflicts

0xa1087a5c…66c4

0x754704…b603

10 touches
10 conflicts

0x002fed35…79fa

0x2a68ba…90c5

8 touches
6 conflicts

0xd67873b6…395a

0x40c49f…2af0

7 touches
6 conflicts

0x6518075e…2b17

0x2a68ba…90c5

6 touches
3 conflicts

0xe3d7c1f1…1f50

0x34b655…2a6f

6 touches
3 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0x170de89a…fb3b

0x40c49f…2af0

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

10 conflicts on slot 0x2b54cadb82…7c4425

← previous block·next block →recent activity