← previous blocknext block →recent activity

Analyzing

Block #72,221,045

9 transactions · 7 stateful · 2026-05-03 19:10:40 UTC

Parallelism

78/100

Blocked

14%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,221,045  ·  9 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xdb80d001…4874

0x065c9d…c394

4 touches
1 conflict

0x7cc28ff0…e277

0x065c9d…c394

3 touches
1 conflict

0x206f76ec…f1ec

0x065c9d…c394

3 touches
1 conflict

0x18bf2a65…005d

0x065c9d…c394

2 touches
0 conflicts

0x20404ffc…74ec

0x065c9d…c394

2 touches
0 conflicts

0x77a88986…e5b8

0x065c9d…c394

2 touches
0 conflicts

0xf9d262f1…5850

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 0x0000000000…00003d

← previous block·next block →recent activity