Block #71,065,234

← previous blocknext block →recent activity

Analyzing

Block #71,065,234

9 transactions · 9 stateful · 2026-04-28 10:47:06 UTC

Parallelism

56/100

Blocked

33%

Avg conflicts / tx

0.67

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #71,065,234  ·  9 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

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x5ff9e831…6008

0x065c9d…c394

8 touches
6 conflicts

0x3887fda3…e122

0x065c9d…c394

7 touches
6 conflicts

0xf5f3a257…0b34

0x065c9d…c394

6 touches
3 conflicts

0xd21dfa54…8723

0x065c9d…c394

6 touches
3 conflicts

0x10b5ff2e…ea9b

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0004

0xd0f8a6…badc

6 touches
3 conflicts

0xcf51f16a…489e

0x065c9d…c394

3 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: 0x065c9d28…a9c394

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity