← previous blocknext block →recent activity

Analyzing

Block #95,173,194

18 transactions · 18 stateful · 2026-08-11 21:50:59 UTC

Parallelism

44/100

Blocked

61%

Avg conflicts / tx

2.06

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #95,173,194  ·  18 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

16 touches
28 conflicts

0xa1087a5c…66c4

0x754704…b603

16 touches
28 conflicts

0x889d5e90…929a

0x2a68ba…90c5

10 touches
10 conflicts

0x6518075e…2b17

0x2a68ba…90c5

8 touches
6 conflicts

0x345a469c…de81

0x40c49f…2af0

8 touches
6 conflicts

0xc8e1abfd…835b

0x40c49f…2af0

4 touches
1 conflict

0x3040553c…5e28

0x754704…b603

4 touches
1 conflict

0x4c1fbdf6…953d

0x754704…b603

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)

28 conflicts on slot 0x2b54cadb82…7c4425

← previous block·next block →recent activity