← previous blocknext block →recent activity

Analyzing

Block #98,742,581

25 transactions · 23 stateful · 2026-08-24 11:11:13 UTC

Parallelism

72/100

Blocked

52%

Avg conflicts / tx

1.4

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #98,742,581  ·  25 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

12 touches
15 conflicts

0xa1087a5c…66c4

0x754704…b603

12 touches
15 conflicts

0x6518075e…2b17

0x2a68ba…90c5

10 touches
10 conflicts

0xf7030e94…9d81

0x40c49f…2af0

10 touches
10 conflicts

0xc4b36c74…fd58

0xd32edf…ff58

9 touches
10 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…0019

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0029

0x1b6862…e19c

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)

15 conflicts on slot 0x2b54cadb82…7c4425

← previous block·next block →recent activity