Block #72,394,945

← previous blocknext block →recent activity

Analyzing

Block #72,394,945

21 transactions · 11 stateful · 2026-05-04 14:33:31 UTC

Parallelism

90/100

Blocked

9%

Avg conflicts / tx

0.05

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,394,945  ·  21 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x4decc0f4…164c

0x34b655…2a6f

4 touches
1 conflict

0xadac4a86…c2bc

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x12309510…0ac2

0x000000…012a

2 touches
0 conflicts

0x7b43f938…3650

0x000000…012a

2 touches
0 conflicts

0x4dd1db39…a994

0x188d58…ea8e

2 touches
0 conflicts

0x4dd1db39…a996

0x188d58…ea8e

2 touches
0 conflicts

0x22e0cc1d…ad04

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

1 conflict on slot 0x4decc0f467…4d164c

← previous block·next block →recent activity