← previous blocknext block →recent activity

Analyzing

Block #71,742,235

10 transactions · 9 stateful · 2026-05-01 13:59:38 UTC

Parallelism

70/100

Blocked

22%

Avg conflicts / tx

0.2

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,742,235  ·  10 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

0x692a3bf2…13ff

0x065c9d…c394

4 touches
1 conflict

0x654262d2…869a

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x7463b400…caf1

0xd32edf…ff58

3 touches
1 conflict

0x43b36188…037a

0x065c9d…c394

3 touches
1 conflict

0xc107e3f8…5052

0x065c9d…c394

3 touches
1 conflict

0xe00cbd3c…4ffc

0x065c9d…c394

3 touches
1 conflict

0xf2686193…1aff

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 0x692a3bf235…6213ff

← previous block·next block →recent activity