← previous blocknext block →recent activity

Analyzing

Block #72,431,017

10 transactions · 10 stateful · 2026-05-04 18:33:52 UTC

Parallelism

80/100

Blocked

10%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,431,017  ·  10 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

0xcf41bef6…b6fd

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x28b6be37…1d03

0x065c9d…c394

3 touches
1 conflict

0x15d6503e…8949

0x065c9d…c394

3 touches
1 conflict

0x16c0eeb6…c088

0x065c9d…c394

2 touches
0 conflicts

0x560ba993…53a6

0x065c9d…c394

2 touches
0 conflicts

0x90a6030d…08e3

0x065c9d…c394

2 touches
0 conflicts

0x9f7a2132…643b

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 0xcf41bef6c3…6fb6fd

← previous block·next block →recent activity