← previous blocknext block →recent activity

Analyzing

Block #100,855,409

29 transactions · 18 stateful · 2026-08-31 20:48:54 UTC

Parallelism

79/100

Blocked

44%

Avg conflicts / tx

0.66

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #100,855,409  ·  29 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

12 touches
15 conflicts

0xa1087a5c…66c4

0x754704…b603

10 touches
10 conflicts

0x002fed35…79fa

0x2a68ba…90c5

6 touches
3 conflicts

0x6518075e…2b17

0x2a68ba…90c5

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x8372aaea…fe8a

0x40c49f…2af0

6 touches
3 conflicts

0xe7bc3d1c…0d86

0x40c49f…2af0

6 touches
3 conflicts

0x09106a95…1467

0x33176b…e078

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