← previous blocknext block →recent activity

Analyzing

Block #74,344,316

18 transactions · 14 stateful · 2026-05-13 15:08:06 UTC

Parallelism

83/100

Blocked

29%

Avg conflicts / tx

0.28

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,344,316  ·  18 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xb2d22873…6139

0xd32edf…ff58

5 touches
3 conflicts

0xf3981be5…2c47

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0x7b43f938…3650

0x000000…012a

2 touches
0 conflicts

0x4dd1db39…a994

0x188d58…ea8e

2 touches
0 conflicts

0x4dd1db39…a995

0x188d58…ea8e

2 touches
0 conflicts

0x4dd1db39…a997

0x188d58…ea8e

2 touches
0 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

3 conflicts on slot 0xb2d22873da…e96139

← previous block·next block →recent activity