← previous blocknext block →recent activity

Analyzing

Block #95,202,392

21 transactions · 20 stateful · 2026-08-12 00:17:50 UTC

Parallelism

76/100

Blocked

45%

Avg conflicts / tx

0.71

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #95,202,392  ·  21 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x6518075e…2b17

0x2a68ba…90c5

6 touches
3 conflicts

0x65685341…0647

0x40c49f…2af0

6 touches
3 conflicts

0x261cbea7…e35e

0x34b655…2a6f

4 touches
1 conflict

0x5c1e4658…3669

0x34b655…2a6f

4 touches
1 conflict

0x5f752320…7f90

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

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