Block #72,371,203

← previous blocknext block →recent activity

Analyzing

Block #72,371,203

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

Parallelism

78/100

Blocked

14%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0x81f76c8c…a0c7

0x065c9d…c394

4 touches
1 conflict

0xe60e6a14…f406

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0c4875d8…0814

0x065c9d…c394

4 touches
1 conflict

0x9d1373e6…6ea8

0x065c9d…c394

3 touches
1 conflict

0xec288e92…fa7f

0x065c9d…c394

3 touches
1 conflict

0x4d645db9…f6a7

0x065c9d…c394

3 touches
1 conflict

0x9eb9e719…902c

0x065c9d…c394

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: 0x065c9d28…a9c394

1 conflict on slot 0x81f76c8cfd…eba0c7

← previous block·next block →recent activity