Block #71,000,205

← previous blocknext block →recent activity

Analyzing

Block #71,000,205

25 transactions · 21 stateful · 2026-04-28 03:34:13 UTC

Parallelism

64/100

Blocked

52%

Avg conflicts / tx

1.12

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #71,000,205  ·  25 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x8e39f652…dac3

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x17a7f697…dcb7

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001e

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002e

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

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

21 conflicts on slot 0x8e39f65258…44dac3

← previous block·next block →recent activity