← previous blocknext block →recent activity

Analyzing

Block #70,910,827

14 transactions · 13 stateful · 2026-04-27 17:39:00 UTC

Parallelism

71/100

Blocked

54%

Avg conflicts / tx

0.86

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #70,910,827  ·  14 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

0x92d610a6…9a40

0x2a68ba…90c5

8 touches
6 conflicts

0x24968e6d…0132

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0004

0xd0f8a6…badc

6 touches
3 conflicts

0x53b4ef2b…8a05

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xd32f8498…be67

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0000

0x8fd63a…536c

6 touches
3 conflicts

0x00000000…0001

0x8fd63a…536c

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: 0x2a68ba18…8e90c5

6 conflicts on slot 0x92d610a6f9…379a40

← previous block·next block →recent activity