Block #71,701,202

← previous blocknext block →recent activity

Analyzing

Block #71,701,202

10 transactions · 7 stateful · 2026-05-01 09:26:19 UTC

Parallelism

80/100

Blocked

14%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,701,202  ·  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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x26dd14d2…ccfe

0x065c9d…c394

4 touches
1 conflict

0x7f3201af…2c04

0x065c9d…c394

3 touches
1 conflict

0x0d1ee4ca…2665

0x065c9d…c394

2 touches
0 conflicts

0x138e3f85…9271

0x065c9d…c394

2 touches
0 conflicts

0x26f14ef6…74bd

0x065c9d…c394

2 touches
0 conflicts

0x3d4bcef4…57e6

0x065c9d…c394

2 touches
0 conflicts

0x41755291…977f

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