Block #72,283,732

← previous blocknext block →recent activity

Analyzing

Block #72,283,732

10 transactions · 9 stateful · 2026-05-04 02:11:53 UTC

Parallelism

70/100

Blocked

33%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,283,732  ·  10 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

0xbad68552…e6bf

0x34b655…2a6f

6 touches
3 conflicts

0xf06c2cf5…61bd

0x34b655…2a6f

4 touches
1 conflict

0x2d2b8493…6045

0x34b655…2a6f

4 touches
1 conflict

0x2eaef64d…7f82

0x34b655…2a6f

4 touches
1 conflict

0x388f889f…a655

0x34b655…2a6f

4 touches
1 conflict

0x7cee1be1…e770

0x34b655…2a6f

4 touches
1 conflict

0x85a88798…f85e

0x34b655…2a6f

4 touches
1 conflict

0x8d0e98f3…7ba0

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 0xbad6855239…f0e6bf

← previous block·next block →recent activity