Block #72,288,214

← previous blocknext block →recent activity

Analyzing

Block #72,288,214

6 transactions · 6 stateful · 2026-05-04 02:42:03 UTC

Parallelism

67/100

Blocked

17%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,288,214  ·  6 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

0x9dc9fa5f…7f23

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xe54a1f6f…18f2

0x34b655…2a6f

4 touches
1 conflict

0x08058e4d…cef7

0x065c9d…c394

2 touches
0 conflicts

0x38ba9ea1…9262

0x065c9d…c394

2 touches
0 conflicts

0x54bfda47…ba88

0x065c9d…c394

2 touches
0 conflicts

0xe23556df…ffe5

0x065c9d…c394

2 touches
0 conflicts

0x207c32d3…d39b

0x34b655…2a6f

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: 0x34b6552d…112a6f

1 conflict on slot 0x9dc9fa5fdc…257f23

← previous block·next block →recent activity