← previous blocknext block →recent activity

Analyzing

Block #75,309,759

26 transactions · 14 stateful · 2026-05-18 02:37:28 UTC

Parallelism

85/100

Blocked

43%

Avg conflicts / tx

0.38

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #75,309,759  ·  26 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

0xe100e6f9…d81e

0xd32edf…ff58

7 touches
6 conflicts

0x09106a95…1467

0x33176b…e078

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x3df7769a…5d17

0x3bd359…433a

4 touches
1 conflict

0x63f5c02f…6853

0x3bd359…433a

4 touches
1 conflict

0x00000000…0000

0x850662…52d0

4 touches
1 conflict

0x00000000…0003

0x850662…52d0

4 touches
1 conflict

0x00000000…0004

0x850662…52d0

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: 0xd32edf66…9fff58

6 conflicts on slot 0xe100e6f945…5ad81e

← previous block·next block →recent activity