← previous blocknext block →recent activity

Analyzing

Block #74,356,076

39 transactions · 33 stateful · 2026-05-13 16:26:17 UTC

Parallelism

74/100

Blocked

58%

Avg conflicts / tx

1.26

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,356,076  ·  39 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xb7064d19…01a5

0xd32edf…ff58

11 touches
15 conflicts

0x47b807a2…3307

0x065c9d…c394

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x41755291…977f

0x065c9d…c394

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001a

0x1b6862…e19c

8 touches
6 conflicts

0xcb45d9d6…cb82

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 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

15 conflicts on slot 0xb7064d19c2…f501a5

← previous block·next block →recent activity