← previous blocknext block →recent activity

Analyzing

Block #72,500,723

17 transactions · 11 stateful · 2026-05-05 02:18:04 UTC

Parallelism

88/100

Blocked

27%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,500,723  ·  17 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

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x00000000…0002

0x7e9d3a…9fda

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xde74d6d1…9422

0x065c9d…c394

3 touches
1 conflict

0xa68fda9e…8d47

0x065c9d…c394

2 touches
0 conflicts

0xa7fdb62b…4310

0x065c9d…c394

2 touches
0 conflicts

0xae14798d…5b45

0x065c9d…c394

2 touches
0 conflicts

0xb0db6f20…af34

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: 0x681e908b…e1ae09

1 conflict on slot 0x0d622e34f9…000000

← previous block·next block →recent activity