← previous blocknext block →recent activity

Analyzing

Block #74,351,397

35 transactions · 26 stateful · 2026-05-13 15:55:06 UTC

Parallelism

80/100

Blocked

62%

Avg conflicts / tx

1.23

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,351,397  ·  35 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

0x8bd46f4a…0138

0xd32edf…ff58

13 touches
21 conflicts

0xcb45d9d6…cb81

0x1b6862…e19c

8 touches
6 conflicts

0x8c49c85c…ee96

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0019

0x1b6862…e19c

8 touches
6 conflicts

0xac8e97a0…8426

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

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

21 conflicts on slot 0x8bd46f4a5e…1d0138

← previous block·next block →recent activity