Block #71,041,919

← previous blocknext block →recent activity

Analyzing

Block #71,041,919

10 transactions · 8 stateful · 2026-04-28 08:11:53 UTC

Parallelism

60/100

Blocked

50%

Avg conflicts / tx

0.7

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #71,041,919  ·  10 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xe27b0829…3d3e

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…002f

0x1b6862…e19c

4 touches
1 conflict

0xd53220ed…473b

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x3bc444cc…88da

0x065c9d…c394

4 touches
1 conflict

0x6f7962c8…8c5c

0x065c9d…c394

4 touches
1 conflict

0xac9fc41c…e8bc

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

6 conflicts on slot 0xe27b082925…5c3d3e

← previous block·next block →recent activity