Block #72,371,180

← previous blocknext block →recent activity

Analyzing

Block #72,371,180

8 transactions · 7 stateful · 2026-05-04 11:55:05 UTC

Parallelism

75/100

Blocked

14%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,371,180  ·  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

0x0c4875d8…0814

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x14d3c998…09c8

0x065c9d…c394

3 touches
1 conflict

0xad415ceb…201b

0x065c9d…c394

3 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

2 touches
0 conflicts

0x67485125…eaa4

0x065c9d…c394

2 touches
0 conflicts

0x81f76c8c…a0c7

0x065c9d…c394

2 touches
0 conflicts

0xeb333682…0791

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 0x0c4875d8af…9c0814

← previous block·next block →recent activity