Block #71,090,067

← previous blocknext block →recent activity

Analyzing

Block #71,090,067

21 transactions · 17 stateful · 2026-04-28 13:32:38 UTC

Parallelism

76/100

Blocked

41%

Avg conflicts / tx

0.76

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #71,090,067  ·  21 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x32cca143…e5ad

0xd32edf…ff58

9 touches
10 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

6 touches
3 conflicts

0x304abe7d…f2a5

0x065c9d…c394

4 touches
3 conflicts

0xfe2bac2b…2cec

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x82c6229a…6a1a

0x065c9d…c394

4 touches
1 conflict

0x00000000…0018

0x1b6862…e19c

4 touches
1 conflict

0xcb45d9d6…cb80

0x1b6862…e19c

4 touches
1 conflict

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: 0xd32edf66…9fff58

10 conflicts on slot 0x32cca143e7…e4e5ad

← previous block·next block →recent activity