← previous blocknext block →recent activity

Analyzing

Block #74,248,585

33 transactions · 27 stateful · 2026-05-13 04:31:27 UTC

Parallelism

82/100

Blocked

48%

Avg conflicts / tx

0.85

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,248,585  ·  33 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

0x9b416055…92bb

0xd32edf…ff58

9 touches
10 conflicts

0x768cffcd…2648

0x34b655…2a6f

8 touches
6 conflicts

0xf823e97f…2ee6

0x065c9d…c394

8 touches
6 conflicts

0xcb45d9d6…cb87

0x1b6862…e19c

6 touches
3 conflicts

0x71e96b74…abe9

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xcf3283ba…c9fa

0x065c9d…c394

6 touches
3 conflicts

0x00000000…001f

0x1b6862…e19c

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: 0xd32edf66…9fff58

10 conflicts on slot 0x9b41605552…1292bb

← previous block·next block →recent activity