← previous blocknext block →recent activity

Analyzing

Block #75,502,236

30 transactions · 19 stateful · 2026-05-19 00:07:49 UTC

Parallelism

87/100

Blocked

53%

Avg conflicts / tx

0.63

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #75,502,236  ·  30 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

0x3a9149df…72e0

0x34b655…2a6f

8 touches
6 conflicts

0x15698ac9…2a46

0x34b655…2a6f

8 touches
6 conflicts

0xcb45d9d6…cb80

0x1b6862…e19c

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xc2d4d818…7182

0x34b655…2a6f

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x443a3e47…f4a4

0x065c9d…c394

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: 0x34b6552d…112a6f

6 conflicts on slot 0x3a9149dfdf…6c72e0

← previous block·next block →recent activity