← previous blocknext block →recent activity

Analyzing

Block #73,343,521

18 transactions · 11 stateful · 2026-05-08 23:50:08 UTC

Parallelism

83/100

Blocked

27%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,343,521  ·  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

0x1b020203…9a9f

0x065c9d…c394

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

6 touches
3 conflicts

0xecdec867…5b18

0xd32edf…ff58

5 touches
3 conflicts

0x846f2172…fd54

0x0555e3…2b9c

2 touches
0 conflicts

0x09beabbc…065c

0x188d58…ea8e

2 touches
0 conflicts

0x09beabbc…065e

0x188d58…ea8e

2 touches
0 conflicts

0x46cb45de…a566

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: 0x065c9d28…a9c394

3 conflicts on slot 0x1b020203d2…f19a9f

← previous block·next block →recent activity