Block #72,228,468

← previous blocknext block →recent activity

Analyzing

Block #72,228,468

8 transactions · 8 stateful · 2026-05-03 20:00:27 UTC

Parallelism

75/100

Blocked

25%

Avg conflicts / tx

0.25

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,228,468  ·  8 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

0x28c180e1…f1e2

0x34b655…2a6f

4 touches
1 conflict

0x2965e2d6…5800

0x34b655…2a6f

4 touches
1 conflict

0x41d3bfa5…523e

0x34b655…2a6f

4 touches
1 conflict

0x8c49c85c…ee96

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xdf30b85a…4199

0x34b655…2a6f

4 touches
1 conflict

0xec04039a…3c44

0x34b655…2a6f

4 touches
1 conflict

0xf06e862e…1e01

0xd32edf…ff58

3 touches
1 conflict

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 0x28c180e141…a4f1e2

← previous block·next block →recent activity