Block #72,233,626

← previous blocknext block →recent activity

Analyzing

Block #72,233,626

17 transactions · 11 stateful · 2026-05-03 20:35:08 UTC

Parallelism

76/100

Blocked

27%

Avg conflicts / tx

0.29

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,233,626  ·  17 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xf8f1e808…a4fd

0x34b655…2a6f

4 touches
1 conflict

0x35b85d8e…1edd

0x34b655…2a6f

4 touches
1 conflict

0x2ed00f98…da9f

0x34b655…2a6f

4 touches
1 conflict

0xee0b2bd0…28d5

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x6d971740…9263

0x34b655…2a6f

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 0xac2a02739b…81721b

← previous block·next block →recent activity