Block #71,701,920

← previous blocknext block →recent activity

Analyzing

Block #71,701,920

21 transactions · 16 stateful · 2026-05-01 09:31:07 UTC

Parallelism

71/100

Blocked

38%

Avg conflicts / tx

0.62

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #71,701,920  ·  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

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

8 touches
6 conflicts

0xdc198d80…6d73

0x065c9d…c394

7 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x1c83cb22…fbd3

0xd32edf…ff58

5 touches
3 conflicts

0x7bf9014c…69e0

0x065c9d…c394

4 touches
1 conflict

0x3f4a7626…91e5

0x188d58…ea8e

4 touches
1 conflict

0xe75ce681…ba5f

0x188d58…ea8e

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: 0x754704bc…afb603

6 conflicts on slot 0x17606ba612…ea1b6e

← previous block·next block →recent activity