← previous blocknext block →recent activity

Analyzing

Block #71,092,165

33 transactions · 29 stateful · 2026-04-28 13:46:36 UTC

Parallelism

76/100

Blocked

52%

Avg conflicts / tx

1.09

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #71,092,165  ·  33 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x046a928e…0012

0x2a68ba…90c5

12 touches
15 conflicts

0x8c49c85c…ee96

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x41755291…977f

0x131a2e…0da9

6 touches
3 conflicts

0x00000000…003d

0x131a2e…0da9

6 touches
3 conflicts

0x41755291…977f

0x065c9d…c394

6 touches
3 conflicts

0x47b807a2…3307

0x065c9d…c394

6 touches
3 conflicts

0xb4852205…cdc5

0xd32edf…ff58

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

15 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity