Block #71,696,683

← previous blocknext block →recent activity

Analyzing

Block #71,696,683

21 transactions · 16 stateful · 2026-05-01 08:56:19 UTC

Parallelism

76/100

Blocked

44%

Avg conflicts / tx

0.81

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #71,696,683  ·  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

0x282630d2…69ec

0xd32edf…ff58

9 touches
10 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x17748826…421d

0x065c9d…c394

5 touches
3 conflicts

0x46cb45de…a567

0x188d58…ea8e

4 touches
1 conflict

0x46cb45de…a566

0x188d58…ea8e

4 touches
1 conflict

0x846f2172…fd54

0x0555e3…2b9c

4 touches
1 conflict

0x41755291…977f

0x065c9d…c394

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

10 conflicts on slot 0x282630d270…1169ec

← previous block·next block →recent activity