← previous blocknext block →recent activity

Analyzing

Block #74,762,938

31 transactions · 27 stateful · 2026-05-15 13:44:44 UTC

Parallelism

84/100

Blocked

59%

Avg conflicts / tx

0.94

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,762,938  ·  31 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x0d622e34…0000

0x681e90…ae09

8 touches
6 conflicts

0x443a3e47…f4a4

0x065c9d…c394

8 touches
6 conflicts

0x5929bce3…ea01

0x34b655…2a6f

8 touches
6 conflicts

0x0eac6378…36f4

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x28c180e1…f1e2

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

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: 0x681e908b…e1ae09

6 conflicts on slot 0x0d622e34f9…000000

← previous block·next block →recent activity