Block #72,571,507

← previous blocknext block →recent activity

Analyzing

Block #72,571,507

9 transactions · 6 stateful · 2026-05-05 10:09:20 UTC

Parallelism

78/100

Blocked

17%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,571,507  ·  9 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

0x95b2bb34…cb82

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x82e6c925…2061

0x065c9d…c394

3 touches
1 conflict

0x4e0f5fa3…0d96

0x065c9d…c394

3 touches
1 conflict

0x1e7c05ed…2f58

0x065c9d…c394

2 touches
0 conflicts

0x3d32c204…53fe

0x065c9d…c394

2 touches
0 conflicts

0xc0b1105a…3936

0x065c9d…c394

2 touches
0 conflicts

0xf5a2dea6…c888

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 0x95b2bb34c8…78cb82

← previous block·next block →recent activity