Block #71,416,618

← previous blocknext block →recent activity

Analyzing

Block #71,416,618

11 transactions · 9 stateful · 2026-04-30 01:47:34 UTC

Parallelism

64/100

Blocked

56%

Avg conflicts / tx

1

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #71,416,618  ·  11 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x313f331f…d2ef

0xd32edf…ff58

7 touches
6 conflicts

0x281c5fe6…55f1

0x065c9d…c394

7 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

6 touches
3 conflicts

0xe75ce681…ba5f

0x188d58…ea8e

4 touches
1 conflict

0xe01158fd…f983

0x1b6862…e19c

4 touches
1 conflict

0x0dbf9688…c6cf

0xd18b7e…414b

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

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

6 conflicts on slot 0x313f331f44…e9d2ef

← previous block·next block →recent activity