← previous blocknext block →recent activity

Analyzing

Block #72,572,884

7 transactions · 6 stateful · 2026-05-05 10:18:32 UTC

Parallelism

71/100

Blocked

17%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,572,884  ·  7 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

0x8d4bebe2…42f4

0x065c9d…c394

4 touches
1 conflict

0x81a80ae1…4f11

0x065c9d…c394

3 touches
1 conflict

0x44914f8b…ed56

0x065c9d…c394

3 touches
1 conflict

0x598c02a9…378e

0x065c9d…c394

2 touches
0 conflicts

0x79af385d…7c4c

0x065c9d…c394

2 touches
0 conflicts

0x7bdc89f2…eaec

0x065c9d…c394

2 touches
0 conflicts

0x838a54c6…30a7

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