Block #71,065,377

← previous blocknext block →recent activity

Analyzing

Block #71,065,377

10 transactions · 9 stateful · 2026-04-28 10:48:03 UTC

Parallelism

60/100

Blocked

33%

Avg conflicts / tx

0.6

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

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

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x199d2ea8…8cc3

0x065c9d…c394

6 touches
3 conflicts

0x222ae6f9…c592

0x065c9d…c394

6 touches
3 conflicts

0xac9fc41c…e8bc

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0004

0xd0f8a6…badc

6 touches
3 conflicts

0x4698c00f…01a6

0x065c9d…c394

3 touches
1 conflict

0xe1ef7276…c14b

0x065c9d…c394

3 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

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