← previous blocknext block →recent activity

Analyzing

Block #72,267,201

22 transactions · 19 stateful · 2026-05-04 00:20:48 UTC

Parallelism

77/100

Blocked

53%

Avg conflicts / tx

0.73

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,267,201  ·  22 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

0x6af306bb…2e81

0x3bd359…433a

8 touches
6 conflicts

0xce8bbe33…b72e

0x3bd359…433a

8 touches
6 conflicts

0xf91b744e…9117

0x754704…b603

8 touches
6 conflicts

0x2f60999a…cc8f

0xd32edf…ff58

7 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x0dbf9688…c6cf

0xd18b7e…414b

6 touches
3 conflicts

0x09beabbc…065c

0x188d58…ea8e

6 touches
3 conflicts

0x09beabbc…065d

0x188d58…ea8e

6 touches
3 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: 0x3bd359c1…15433a

6 conflicts on slot 0x6af306bb1d…092e81

← previous block·next block →recent activity