Block #71,742,447

← previous blocknext block →recent activity

Analyzing

Block #71,742,447

22 transactions · 19 stateful · 2026-05-01 14:01:02 UTC

Parallelism

68/100

Blocked

37%

Avg conflicts / tx

0.68

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #71,742,447  ·  22 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x8be8b8ed…33be

0xd32edf…ff58

9 touches
10 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

6 touches
3 conflicts

0xd5d1fa33…9c04

0x065c9d…c394

5 touches
3 conflicts

0xb6d6d740…e91f

0x1b6862…e19c

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

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 0x8be8b8edd4…7233be

← previous block·next block →recent activity