← previous blocknext block →recent activity

Analyzing

Block #74,922,089

30 transactions · 24 stateful · 2026-05-16 07:26:46 UTC

Parallelism

77/100

Blocked

42%

Avg conflicts / tx

0.6

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,922,089  ·  30 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x2b8cae18…2c01

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xcb45d9d6…cb85

0x1b6862…e19c

4 touches
1 conflict

0x10f5f4d8…572e

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x664bf99e…0a8c

0x34b655…2a6f

4 touches
1 conflict

0x781f022e…bf47

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 0x2b8cae1824…b62c01

← previous block·next block →recent activity