Block #70,911,362

← previous blocknext block →recent activity

Analyzing

Block #70,911,362

37 transactions · 22 stateful · 2026-04-27 17:42:34 UTC

Parallelism

84/100

Blocked

50%

Avg conflicts / tx

0.73

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #70,911,362  ·  37 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x26a52318…f551

0xd32edf…ff58

11 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0002

0xb857c1…9be1

6 touches
3 conflicts

0xb02fe354…948e

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0000

0x1f86a9…17ed

4 touches
1 conflict

0x00000000…0002

0x1f86a9…17ed

4 touches
1 conflict

0x00000000…0004

0x1f86a9…17ed

4 touches
1 conflict

0x92d610a6…9a40

0x2a68ba…90c5

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

15 conflicts on slot 0x26a523180b…85f551

← previous block·next block →recent activity