Block #71,092,290

← previous blocknext block →recent activity

Analyzing

Block #71,092,290

36 transactions · 29 stateful · 2026-04-28 13:47:26 UTC

Parallelism

81/100

Blocked

69%

Avg conflicts / tx

1.53

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #71,092,290  ·  36 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xda75c66c…bc6d

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…003d

0x065c9d…c394

12 touches
15 conflicts

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…003d

0x131a2e…0da9

6 touches
3 conflicts

0x41755291…977f

0x065c9d…c394

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x8c49c85c…ee96

0x34b655…2a6f

6 touches
3 conflicts

0x912b7bc7…1af9

0x34b655…2a6f

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

21 conflicts on slot 0xda75c66c25…5bbc6d

← previous block·next block →recent activity