Block #72,213,559

← previous blocknext block →recent activity

Analyzing

Block #72,213,559

5 transactions · 4 stateful · 2026-05-03 18:20:21 UTC

Parallelism

60/100

Blocked

25%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,213,559  ·  5 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xb27de525…ce1b

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xf251cd1b…7faa

0x065c9d…c394

3 touches
1 conflict

0x11d01c33…3290

0x065c9d…c394

3 touches
1 conflict

0x2d750eac…2c1e

0x065c9d…c394

2 touches
0 conflicts

0x47b807a2…3307

0x065c9d…c394

2 touches
0 conflicts

0x9f56afc7…418b

0x065c9d…c394

2 touches
0 conflicts

0xc73f2e86…fb70

0x065c9d…c394

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

1 conflict on slot 0xb27de5259d…77ce1b

← previous block·next block →recent activity