Block #71,037,459

← previous blocknext block →recent activity

Analyzing

Block #71,037,459

10 transactions · 10 stateful · 2026-04-28 07:42:13 UTC

Parallelism

80/100

Blocked

20%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,037,459  ·  10 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x4dd258f0…919f

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xa883b3de…9630

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x3542f402…91b6

0x065c9d…c394

3 touches
1 conflict

0x3ac20dc5…896a

0x065c9d…c394

3 touches
1 conflict

0x06ba7fe9…110c

0xd32edf…ff58

3 touches
1 conflict

0x00000000…002f

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

1 conflict on slot 0x4dd258f00a…e9919f

← previous block·next block →recent activity