Block #72,167,251

← previous blocknext block →recent activity

Analyzing

Block #72,167,251

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

Parallelism

67/100

Blocked

36%

Avg conflicts / tx

0.58

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,167,251  ·  12 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

0x8a35acfb…d1ac

0x8d66a4…3095

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x3254d19b…f714

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x76eb9e75…d982

0x34b655…2a6f

4 touches
1 conflict

0x143dba04…1b98

0x8d66a4…3095

4 touches
1 conflict

0x1e451306…7993

0x8d66a4…3095

4 touches
1 conflict

0x462c8be7…4f83

0x8d66a4…3095

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: 0x8d66a43f…113095

6 conflicts on slot 0x8a35acfbc1…6bd1ac

← previous block·next block →recent activity