Block #71,284,487

← previous blocknext block →recent activity

Analyzing

Block #71,284,487

21 transactions · 19 stateful · 2026-04-29 11:06:46 UTC

Parallelism

62/100

Blocked

58%

Avg conflicts / tx

1.38

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #71,284,487  ·  21 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

0xe54a1f6f…18f2

0x34b655…2a6f

12 touches
15 conflicts

0xf0a7ca33…3c7e

0x34b655…2a6f

10 touches
10 conflicts

0xf853eb8e…4027

0x34b655…2a6f

10 touches
10 conflicts

0xaa3492db…3703

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x6eba5e7f…4b52

0x34b655…2a6f

6 touches
3 conflicts

0x77905798…fe3d

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

15 conflicts on slot 0xe54a1f6fdd…7918f2

← previous block·next block →recent activity