Block #71,709,004

← previous blocknext block →recent activity

Analyzing

Block #71,709,004

13 transactions · 10 stateful · 2026-05-01 10:18:12 UTC

Parallelism

85/100

Blocked

10%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,709,004  ·  13 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xff114c8c…5a0a

0x065c9d…c394

4 touches
1 conflict

0x2e9ce705…77e5

0x065c9d…c394

3 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

2 touches
0 conflicts

0x54abf48f…eac1

0x065c9d…c394

2 touches
0 conflicts

0x885e8cc5…e826

0x065c9d…c394

2 touches
0 conflicts

0xb8d901f5…e0ed

0x065c9d…c394

2 touches
0 conflicts

0xfec2e3d7…dfd9

0x065c9d…c394

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 0x0000000000…00003d

← previous block·next block →recent activity