Block #72,288,125

← previous blocknext block →recent activity

Analyzing

Block #72,288,125

25 transactions · 18 stateful · 2026-05-04 02:41:27 UTC

Parallelism

80/100

Blocked

67%

Avg conflicts / tx

0.92

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,288,125  ·  25 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

0xbbdeb513…4465

0xd32edf…ff58

9 touches
10 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0xbb1747e2…f78b

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

4 touches
1 conflict

0x9e0e23b5…6910

0x34b655…2a6f

4 touches
1 conflict

0xb96e29a5…0419

0x34b655…2a6f

4 touches
1 conflict

0xc3aacf13…6b3d

0x34b655…2a6f

4 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: 0xd32edf66…9fff58

10 conflicts on slot 0xbbdeb5131f…094465

← previous block·next block →recent activity