Block #72,214,136

← previous blocknext block →recent activity

Analyzing

Block #72,214,136

8 transactions · 6 stateful · 2026-05-03 18:24:12 UTC

Parallelism

75/100

Blocked

17%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,214,136  ·  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

0x21f5dc3c…dd58

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x88d63774…f663

0x065c9d…c394

3 touches
1 conflict

0x0af0537b…5fbf

0x065c9d…c394

2 touches
0 conflicts

0x27f32b4e…b25e

0x065c9d…c394

2 touches
0 conflicts

0x2d0de12e…3972

0x065c9d…c394

2 touches
0 conflicts

0x41755291…977f

0x065c9d…c394

2 touches
0 conflicts

0x47b807a2…3307

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 0x21f5dc3c8b…ccdd58

← previous block·next block →recent activity