Block #72,283,322

← previous blocknext block →recent activity

Analyzing

Block #72,283,322

15 transactions · 13 stateful · 2026-05-04 02:09:08 UTC

Parallelism

73/100

Blocked

31%

Avg conflicts / tx

0.4

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,283,322  ·  15 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

0xbad68552…e6bf

0x34b655…2a6f

6 touches
3 conflicts

0x96504a63…52d2

0x8d66a4…3095

4 touches
1 conflict

0xac808a27…82db

0x34b655…2a6f

4 touches
1 conflict

0xb8228d38…3953

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x8a35acfb…d1ac

0x8d66a4…3095

4 touches
1 conflict

0x49339736…b223

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