← previous blocknext block →recent activity

Analyzing

Block #100,849,589

20 transactions · 20 stateful · 2026-08-31 20:19:37 UTC

Parallelism

65/100

Blocked

45%

Avg conflicts / tx

0.85

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #100,849,589  ·  20 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

0x002fed35…79fa

0x2a68ba…90c5

6 touches
3 conflicts

0xd639efdf…ca3e

0x40c49f…2af0

6 touches
3 conflicts

0x7d863e5b…ca4f

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…002b

0x1b6862…e19c

4 touches
1 conflict

0x91220b8f…7a04

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

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)

10 conflicts on slot 0x2b54cadb82…7c4425

← previous block·next block →recent activity