← previous blocknext block →recent activity

Analyzing

Block #75,478,709

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

Parallelism

79/100

Blocked

54%

Avg conflicts / tx

0.63

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

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

0x96a1fd00…1396

0xd32edf…ff58

7 touches
6 conflicts

0x846f2172…fd54

0x0555e3…2b9c

4 touches
1 conflict

0xee0a9ebb…c425

0x0555e3…2b9c

4 touches
1 conflict

0x09beabbc…065c

0x188d58…ea8e

4 touches
1 conflict

0xe75ce681…ba5f

0x188d58…ea8e

4 touches
1 conflict

0xe75ce681…ba61

0x188d58…ea8e

4 touches
1 conflict

0x99a21305…dffc

0x2a68ba…90c5

4 touches
1 conflict

0x5d82c9b5…004c

0x3bd359…433a

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 0x96a1fd00b1…611396

← previous block·next block →recent activity