← previous blocknext block →recent activity

Analyzing

Block #75,478,958

19 transactions · 13 stateful · 2026-05-18 21:28:03 UTC

Parallelism

79/100

Blocked

31%

Avg conflicts / tx

0.37

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #75,478,958  ·  19 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

0x46cb45de…a566

0x188d58…ea8e

8 touches
6 conflicts

0x46cb45de…a568

0x188d58…ea8e

6 touches
3 conflicts

0x00000000…0000

0x614b85…a284

4 touches
1 conflict

0x00000000…0002

0x614b85…a284

4 touches
1 conflict

0x00000000…0004

0x614b85…a284

4 touches
1 conflict

0x0dbf9688…c6cf

0xd18b7e…414b

4 touches
1 conflict

0x751db0c0…4f57

0xd18b7e…414b

4 touches
1 conflict

0x09beabbc…065c

0x188d58…ea8e

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: 0x188d586d…f9ea8e

6 conflicts on slot 0x46cb45de01…66a566

← previous block·next block →recent activity