← previous blocknext block →recent activity

Analyzing

Block #72,979,401

21 transactions · 15 stateful · 2026-05-07 07:27:25 UTC

Parallelism

71/100

Blocked

40%

Avg conflicts / tx

0.86

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #72,979,401  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x1d92aebc…70f5

0xd32edf…ff58

11 touches
15 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x0b390c61…dc07

0x065c9d…c394

2 touches
0 conflicts

0xf39492aa…fafb

0x065c9d…c394

2 touches
0 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

2 touches
0 conflicts

0x01e7b865…6e6f

0x188d58…ea8e

2 touches
0 conflicts

0x01e7b865…6e70

0x188d58…ea8e

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

15 conflicts on slot 0x1d92aebc6e…7f70f5

← previous block·next block →recent activity