Block #71,558,381

← previous blocknext block →recent activity

Analyzing

Block #71,558,381

10 transactions · 8 stateful · 2026-04-30 17:35:46 UTC

Parallelism

80/100

Blocked

13%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,558,381  ·  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

0xd6aabe89…92f5

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xfa2527aa…9dd5

0x34b655…2a6f

4 touches
1 conflict

0xc13d9ed0…42c6

0x065c9d…c394

2 touches
0 conflicts

0xcccc100d…32c3

0x065c9d…c394

2 touches
0 conflicts

0xda650f3d…8685

0x065c9d…c394

2 touches
0 conflicts

0xe9bab3a3…ff33

0x065c9d…c394

2 touches
0 conflicts

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: 0x34b6552d…112a6f

1 conflict on slot 0xd6aabe893a…bf92f5

← previous block·next block →recent activity