← previous blocknext block →recent activity

Analyzing

Block #72,288,051

21 transactions · 18 stateful · 2026-05-04 02:40:57 UTC

Parallelism

76/100

Blocked

33%

Avg conflicts / tx

0.48

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,288,051  ·  21 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

0x655b83ce…afeb

0xd32edf…ff58

7 touches
6 conflicts

0x6398d3b5…df99

0x065c9d…c394

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x74e71984…ae90

0x2a68ba…90c5

6 touches
3 conflicts

0x37699b20…106f

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

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: 0xd32edf66…9fff58

6 conflicts on slot 0x655b83ce58…76afeb

← previous block·next block →recent activity