← previous blocknext block →recent activity

Analyzing

Block #72,861,183

22 transactions · 21 stateful · 2026-05-06 18:20:38 UTC

Parallelism

86/100

Blocked

24%

Avg conflicts / tx

0.27

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,861,183  ·  22 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xce7bfe5e…5e58

0x065c9d…c394

6 touches
3 conflicts

0x7f189cf6…afab

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x01e7b865…6e6f

0x188d58…ea8e

4 touches
1 conflict

0x70b2f813…783c

0x2a68ba…90c5

4 touches
1 conflict

0xe09eda07…8dda

0x2a68ba…90c5

4 touches
1 conflict

0x0520da1d…c88e

0x34b655…2a6f

4 touches
1 conflict

0x085df2c1…305a

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

3 conflicts on slot 0xce7bfe5ef1…205e58

← previous block·next block →recent activity