← previous blocknext block →recent activity

Analyzing

Block #74,041,532

19 transactions · 14 stateful · 2026-05-12 05:34:00 UTC

Parallelism

74/100

Blocked

36%

Avg conflicts / tx

0.42

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,041,532  ·  19 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

0xe8fd4b48…e2a0

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…002b

0x1b6862…e19c

4 touches
1 conflict

0x2877f440…c2c8

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x85a88798…f85e

0x34b655…2a6f

4 touches
1 conflict

0x35b65947…44d1

0xc8689a…ee79

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xbd7e37a9…9eb5

0x065c9d…c394

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 0xe8fd4b48f5…2be2a0

← previous block·next block →recent activity