← previous blocknext block →recent activity

Analyzing

Block #71,445,791

25 transactions · 21 stateful · 2026-04-30 05:01:57 UTC

Parallelism

84/100

Blocked

48%

Avg conflicts / tx

0.52

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #71,445,791  ·  25 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

0x451e482b…7e7d

0x34b655…2a6f

6 touches
3 conflicts

0x01e7b865…6e6e

0x188d58…ea8e

6 touches
3 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x8bcab68f…396a

0xd32edf…ff58

5 touches
3 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0x23114fac…630a

0x34b655…2a6f

4 touches
1 conflict

0x3254d19b…f714

0x34b655…2a6f

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: 0x34b6552d…112a6f

3 conflicts on slot 0x451e482b59…427e7d

← previous block·next block →recent activity