Block #72,399,810

← previous blocknext block →recent activity

Analyzing

Block #72,399,810

23 transactions · 17 stateful · 2026-05-04 15:05:57 UTC

Parallelism

78/100

Blocked

47%

Avg conflicts / tx

0.39

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,399,810  ·  23 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

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x8a35acfb…d1ad

0x8d66a4…3095

4 touches
1 conflict

0xe89e1a22…ce49

0x8d66a4…3095

4 touches
1 conflict

0x24968e6d…0132

0x065c9d…c394

4 touches
1 conflict

0x4ba1fda1…2acc

0x065c9d…c394

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 0x60f7fbaf90…97bd58

← previous block·next block →recent activity