Block #72,224,393

← previous blocknext block →recent activity

Analyzing

Block #72,224,393

20 transactions · 14 stateful · 2026-05-03 19:33:03 UTC

Parallelism

75/100

Blocked

36%

Avg conflicts / tx

0.35

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,224,393  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x8b7fe709…9d99

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x41755291…977f

0x065c9d…c394

4 touches
1 conflict

0x32aa281b…0f8e

0x34b655…2a6f

4 touches
1 conflict

0x4794062f…2b25

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 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: 0x34b6552d…112a6f

3 conflicts on slot 0x8b7fe70996…af9d99

← previous block·next block →recent activity