← previous blocknext block →recent activity

Analyzing

Block #75,478,918

20 transactions · 16 stateful · 2026-05-18 21:27:47 UTC

Parallelism

80/100

Blocked

50%

Avg conflicts / tx

0.9

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #75,478,918  ·  20 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x0dbf9688…c6cf

0xd18b7e…414b

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0xe75ce681…ba5f

0x188d58…ea8e

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x5086c64a…28ba

0x34b655…2a6f

6 touches
3 conflicts

0x085df2c1…305a

0x34b655…2a6f

6 touches
3 conflicts

0x399d330d…da84

0x34b655…2a6f

6 touches
3 conflicts

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)

6 conflicts on slot 0x0dbf9688de…b0c6cf

← previous block·next block →recent activity