← previous blocknext block →recent activity

Analyzing

Block #74,555,888

29 transactions · 24 stateful · 2026-05-14 14:40:55 UTC

Parallelism

83/100

Blocked

42%

Avg conflicts / tx

0.66

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,555,888  ·  29 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x1ee24099…4d4e

0xd32edf…ff58

7 touches
6 conflicts

0xf3d7a307…4d63

0x065c9d…c394

6 touches
3 conflicts

0xb0485f38…4544

0x065c9d…c394

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x801a6e57…d85c

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x8a35acfb…d1ab

0x8d66a4…3095

5 touches
3 conflicts

0x7c403af1…31b1

0x3bd359…433a

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

6 conflicts on slot 0x1ee240995a…794d4e

← previous block·next block →recent activity