← previous blocknext block →recent activity

Analyzing

Block #70,951,956

11 transactions · 10 stateful · 2026-04-27 22:12:49 UTC

Parallelism

73/100

Blocked

30%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #70,951,956  ·  11 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

0xac298b00…81ef

0xd32edf…ff58

5 touches
3 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0x0cb4971f…e2cd

0x065c9d…c394

3 touches
1 conflict

0x09beabbc…065c

0x188d58…ea8e

2 touches
0 conflicts

0x09beabbc…065d

0x188d58…ea8e

2 touches
0 conflicts

0x46cb45de…a566

0x188d58…ea8e

2 touches
0 conflicts

0x46cb45de…a567

0x188d58…ea8e

2 touches
0 conflicts

0x46cb45de…a569

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 0xac298b0058…5281ef

← previous block·next block →recent activity