← previous blocknext block →recent activity

Analyzing

Block #74,923,330

29 transactions · 26 stateful · 2026-05-16 07:35:06 UTC

Parallelism

72/100

Blocked

54%

Avg conflicts / tx

1.17

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,923,330  ·  29 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x348fda08…7e96

0x065c9d…c394

10 touches
10 conflicts

0x180c3306…1f79

0xd32edf…ff58

9 touches
10 conflicts

0xba38536d…2b7d

0x065c9d…c394

8 touches
6 conflicts

0x083a8763…5a7d

0x1b6862…e19c

6 touches
3 conflicts

0xf853eb8e…4027

0x34b655…2a6f

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

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: 0x065c9d28…a9c394

10 conflicts on slot 0x348fda08cf…fc7e96

← previous block·next block →recent activity