Block #71,627,268

← previous blocknext block →recent activity

Analyzing

Block #71,627,268

38 transactions · 20 stateful · 2026-05-01 01:14:14 UTC

Parallelism

68/100

Blocked

65%

Avg conflicts / tx

1.32

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #71,627,268  ·  38 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0xb6c1dd00…ba35

0xd32edf…ff58

17 touches
36 conflicts

0x17606ba6…1b6e

0x754704…b603

10 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0xba5743c7…21c2

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…002b

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001b

0x1b6862…e19c

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

36 conflicts on slot 0xb6c1dd004a…f1ba35

← previous block·next block →recent activity