Block #71,289,325

← previous blocknext block →recent activity

Analyzing

Block #71,289,325

11 transactions · 9 stateful · 2026-04-29 11:38:55 UTC

Parallelism

82/100

Blocked

11%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,289,325  ·  11 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

0x683fe8c9…78c9

0x065c9d…c394

4 touches
1 conflict

0xc58b7e26…3c5a

0x065c9d…c394

3 touches
1 conflict

0xc0e783db…d1d5

0x065c9d…c394

2 touches
0 conflicts

0xdb962b83…e6be

0x065c9d…c394

2 touches
0 conflicts

0xfe2bac2b…2cec

0x065c9d…c394

2 touches
0 conflicts

0x1627b708…d040

0x2a68ba…90c5

2 touches
0 conflicts

0xde38584a…ecb7

0x2a68ba…90c5

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