← previous blocknext block →recent activity

Analyzing

Block #75,478,683

17 transactions · 13 stateful · 2026-05-18 21:26:11 UTC

Parallelism

76/100

Blocked

31%

Avg conflicts / tx

0.41

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #75,478,683  ·  17 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

0x00000000…0022

0xd2634e…53b1

6 touches
3 conflicts

0xe75ce681…ba5f

0x188d58…ea8e

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x0dbf9688…c6cf

0xd18b7e…414b

6 touches
3 conflicts

0xe92fd8b2…882a

0xd18b7e…414b

6 touches
3 conflicts

0x00000000…0002

0xd2634e…53b1

6 touches
3 conflicts

0x00000000…0003

0xd2634e…53b1

6 touches
3 conflicts

0x00000000…001a

0xd2634e…53b1

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: 0xd2634e05…6653b1

3 conflicts on slot 0x0000000000…000022

← previous block·next block →recent activity