← previous blocknext block →recent activity

Analyzing

Block #95,204,033

15 transactions · 11 stateful · 2026-08-12 00:26:05 UTC

Parallelism

87/100

Blocked

27%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #95,204,033  ·  15 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

0x6518075e…2b17

0x2a68ba…90c5

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

4 touches
1 conflict

0x1ec4c748…7c76

0x34b655…2a6f

4 touches
1 conflict

0x4bfdcd51…9b58

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x52c9f3c6…0cb8

0x40c49f…2af0

4 touches
1 conflict

0xa1087a5c…66c4

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)

1 conflict on slot 0x2b54cadb82…7c4425

← previous block·next block →recent activity