Block #71,422,228

← previous blocknext block →recent activity

Analyzing

Block #71,422,228

8 transactions · 8 stateful · 2026-04-30 02:24:55 UTC

Parallelism

38/100

Blocked

50%

Avg conflicts / tx

1.25

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #71,422,228  ·  8 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

0xf853eb8e…4027

0x34b655…2a6f

8 touches
6 conflicts

0x1c913164…5c2e

0x34b655…2a6f

6 touches
3 conflicts

0x220f4f84…15f8

0x34b655…2a6f

6 touches
3 conflicts

0x908d4442…2c4b

0x34b655…2a6f

6 touches
3 conflicts

0xac8e97a0…8426

0x34b655…2a6f

6 touches
3 conflicts

0xe52133fd…b3a7

0x34b655…2a6f

6 touches
3 conflicts

0x37cfaf01…4a46

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

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: 0x34b6552d…112a6f

6 conflicts on slot 0xf853eb8e72…d84027

← previous block·next block →recent activity