← previous blocknext block →recent activity

Analyzing

Block #72,978,127

20 transactions · 14 stateful · 2026-05-07 07:18:58 UTC

Parallelism

75/100

Blocked

29%

Avg conflicts / tx

0.45

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,978,127  ·  20 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

0xb5996243…380b

0xd32edf…ff58

7 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0xe75ce681…ba61

0x188d58…ea8e

4 touches
1 conflict

0xe75ce681…ba5f

0x188d58…ea8e

4 touches
1 conflict

0x1c70b5f7…d677

0x065c9d…c394

4 touches
1 conflict

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x1a0c3cc5…6c5a

0x754704…b603

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

6 conflicts on slot 0xb5996243bc…b1380b

← previous block·next block →recent activity