Block #71,422,117

← previous blocknext block →recent activity

Analyzing

Block #71,422,117

14 transactions · 12 stateful · 2026-04-30 02:24:10 UTC

Parallelism

64/100

Blocked

33%

Avg conflicts / tx

0.71

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #71,422,117  ·  14 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

0xfcb7b8b2…ebb3

0x065c9d…c394

10 touches
10 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x2557abf8…2901

0x34b655…2a6f

2 touches
0 conflicts

0x3a786feb…5910

0x34b655…2a6f

2 touches
0 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

2 touches
0 conflicts

0x66d471e7…de6b

0x34b655…2a6f

2 touches
0 conflicts

0x6b602543…32e5

0x34b655…2a6f

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: 0x065c9d28…a9c394

10 conflicts on slot 0xfcb7b8b239…6bebb3

← previous block·next block →recent activity