← previous blocknext block →recent activity

Analyzing

Block #72,233,847

11 transactions · 9 stateful · 2026-05-03 20:36:37 UTC

Parallelism

82/100

Blocked

11%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,233,847  ·  11 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

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0f4411d7…9289

0x065c9d…c394

4 touches
1 conflict

0x1543e463…37b4

0x065c9d…c394

3 touches
1 conflict

0xfe214b52…1bef

0x065c9d…c394

3 touches
1 conflict

0xa0f9be8f…ef60

0x065c9d…c394

3 touches
1 conflict

0x1aa09dfd…f22b

0x065c9d…c394

3 touches
1 conflict

0x32964233…9e55

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 0x5c8c6ab6f0…86dc36

← previous block·next block →recent activity