← previous blocknext block →recent activity

Analyzing

Block #95,032,439

10 transactions · 10 stateful · 2026-08-11 10:02:10 UTC

Parallelism

80/100

Blocked

20%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #95,032,439  ·  10 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0x0e618922…ae34

0x968279…9342

4 touches
1 conflict

0x0e618922…ae36

0x968279…9342

4 touches
1 conflict

0x99c0b00c…01f0

0x968279…9342

4 touches
1 conflict

0x99c0b00c…01f1

0x968279…9342

4 touches
1 conflict

0x99c0b00c…01f3

0x968279…9342

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x861c0598…9aed

0x40c49f…2af0

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)

1 conflict on slot 0x2b54cadb82…7c4425

← previous block·next block →recent activity