Block #71,284,408

← previous blocknext block →recent activity

Analyzing

Block #71,284,408

8 transactions · 6 stateful · 2026-04-29 11:06:14 UTC

Parallelism

75/100

Blocked

17%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,284,408  ·  8 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

0x1627b708…d040

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xfe2bac2b…2cec

0x065c9d…c394

4 touches
1 conflict

0x7b53996e…61b7

0x065c9d…c394

2 touches
1 conflict

0x7beb9ff4…c907

0x065c9d…c394

2 touches
1 conflict

0xb0caf300…6c74

0x065c9d…c394

2 touches
0 conflicts

0x0520da1d…c88e

0x34b655…2a6f

2 touches
0 conflicts

0x00000000…000b

0x7dfaf7…bf6a

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: 0x2a68ba18…8e90c5

1 conflict on slot 0x1627b708d5…f6d040

← previous block·next block →recent activity