Block #72,224,416

← previous blocknext block →recent activity

Analyzing

Block #72,224,416

13 transactions · 11 stateful · 2026-05-03 19:33:12 UTC

Parallelism

77/100

Blocked

36%

Avg conflicts / tx

0.46

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,224,416  ·  13 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xa4e3b3b1…0911

0x2a68ba…90c5

4 touches
1 conflict

0xfa678100…047f

0xa6afd3…d132

3 touches
1 conflict

0xe7cbba0f…9372

0xd32edf…ff58

3 touches
1 conflict

0x5ccc1579…359a

0x065c9d…c394

2 touches
0 conflicts

0x80d4eaa9…b1ca

0x065c9d…c394

2 touches
0 conflicts

0x729c91b8…9537

0x188d58…ea8e

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity