← previous blocknext block →recent activity

Analyzing

Block #74,744,958

48 transactions · 32 stateful · 2026-05-15 11:44:16 UTC

Parallelism

77/100

Blocked

75%

Avg conflicts / tx

1.71

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #74,744,958  ·  48 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x669ebc83…ae26

0xd32edf…ff58

19 touches
45 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

12 touches
15 conflicts

0xba38536d…2b7d

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x3e49348b…9445

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x280ab921…93a1

0x065c9d…c394

7 touches
6 conflicts

0xd9f18d9a…141d

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

45 conflicts on slot 0x669ebc83da…85ae26

← previous block·next block →recent activity