Block #70,908,552

← previous blocknext block →recent activity

Analyzing

Block #70,908,552

28 transactions · 23 stateful · 2026-04-27 17:23:52 UTC

Parallelism

61/100

Blocked

61%

Avg conflicts / tx

1.32

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #70,908,552  ·  28 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x1c913164…5c2e

0x34b655…2a6f

10 touches
10 conflicts

0x1179284b…db76

0x34b655…2a6f

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x8a35acfb…d1b0

0x8d66a4…3095

8 touches
6 conflicts

0xf853eb8e…4027

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0002

0xb857c1…9be1

6 touches
3 conflicts

0x6c042c61…f883

0x34b655…2a6f

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity