Block #72,571,216

← previous blocknext block →recent activity

Analyzing

Block #72,571,216

11 transactions · 7 stateful · 2026-05-05 10:07:24 UTC

Parallelism

64/100

Blocked

43%

Avg conflicts / tx

0.36

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,571,216  ·  11 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x612d7d1f…4e7e

0x065c9d…c394

4 touches
1 conflict

0xfc01eef2…0aa4

0x065c9d…c394

4 touches
1 conflict

0x520eccbc…127c

0xd32edf…ff58

3 touches
1 conflict

0x1028f9ad…ef11

0x065c9d…c394

3 touches
1 conflict

0x9bb24330…7722

0x065c9d…c394

3 touches
1 conflict

0xd355bf5d…7ec5

0x065c9d…c394

3 touches
1 conflict

0xcf9df718…9daa

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity