← previous blocknext block →recent activity

Analyzing

Block #74,506,942

12 transactions · 9 stateful · 2026-05-14 09:10:54 UTC

Parallelism

67/100

Blocked

44%

Avg conflicts / tx

0.58

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,506,942  ·  12 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

0xffe431af…8faa

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x10a8c2e8…126f

0x065c9d…c394

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x0119c9b8…cc22

0x1efe02…37d6

2 touches
0 conflicts

0x1c28e67a…9b1a

0x1efe02…37d6

2 touches
0 conflicts

0x995f3998…221b

0x1efe02…37d6

2 touches
0 conflicts

0x0872abbe…9c39

0x2a68ba…90c5

2 touches
0 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: 0x065c9d28…a9c394

6 conflicts on slot 0xffe431af56…838faa

← previous block·next block →recent activity