← previous blocknext block →recent activity

Analyzing

Block #74,290,919

26 transactions · 21 stateful · 2026-05-13 09:12:56 UTC

Parallelism

77/100

Blocked

43%

Avg conflicts / tx

0.77

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,290,919  ·  26 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xf50e6654…0252

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xcf3283ba…c9fa

0x065c9d…c394

6 touches
3 conflicts

0x6b319071…a105

0xc8689a…ee79

6 touches
3 conflicts

0x00000000…0018

0x1b6862…e19c

4 touches
1 conflict

0xcb45d9d6…cb80

0x1b6862…e19c

4 touches
1 conflict

0x765c236f…ff45

0x2a68ba…90c5

4 touches
1 conflict

0x3817764d…242b

0x34b655…2a6f

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

10 conflicts on slot 0xf50e6654f9…e70252

← previous block·next block →recent activity