← previous blocknext block →recent activity

Analyzing

Block #74,026,028

34 transactions · 26 stateful · 2026-05-12 03:51:02 UTC

Parallelism

68/100

Blocked

62%

Avg conflicts / tx

1.65

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #74,026,028  ·  34 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

0x60f7fbaf…bd58

0x34b655…2a6f

16 touches
28 conflicts

0xcda20b31…212c

0xd32edf…ff58

11 touches
15 conflicts

0xf853eb8e…4027

0x34b655…2a6f

10 touches
10 conflicts

0x5de96bd3…c60c

0x34b655…2a6f

10 touches
10 conflicts

0xac8e97a0…8426

0x34b655…2a6f

8 touches
6 conflicts

0x318ac0bb…6b9c

0x34b655…2a6f

8 touches
6 conflicts

0xc6417de0…2191

0xc8689a…ee79

8 touches
6 conflicts

0x4f483049…3cc7

0x34b655…2a6f

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: 0x34b6552d…112a6f

28 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity