← previous blocknext block →recent activity

Analyzing

Block #71,742,233

19 transactions · 14 stateful · 2026-05-01 13:59:37 UTC

Parallelism

84/100

Blocked

21%

Avg conflicts / tx

0.21

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,742,233  ·  19 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

0xa850f42e…7859

0xd32edf…ff58

5 touches
3 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0xffe431af…8faa

0x065c9d…c394

4 touches
1 conflict

0x846f2172…fd54

0x0555e3…2b9c

2 touches
0 conflicts

0xee0a9ebb…c425

0x0555e3…2b9c

2 touches
0 conflicts

0x46cb45de…a566

0x188d58…ea8e

2 touches
0 conflicts

0x46cb45de…a567

0x188d58…ea8e

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

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 0xa850f42ed3…4b7859

← previous block·next block →recent activity