Block #70,845,906

← previous blocknext block →recent activity

Analyzing

Block #70,845,906

20 transactions · 14 stateful · 2026-04-27 10:26:39 UTC

Parallelism

80/100

Blocked

21%

Avg conflicts / tx

0.3

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #70,845,906  ·  20 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

0x0a817609…f9d6

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x42f43512…c641

0x065c9d…c394

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x2ce2d49e…d188

0x1b6862…e19c

4 touches
1 conflict

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x729c91b8…9539

0x188d58…ea8e

2 touches
0 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

6 conflicts on slot 0x0a8176090b…f5f9d6

← previous block·next block →recent activity