Block #70,981,739

← previous blocknext block →recent activity

Analyzing

Block #70,981,739

14 transactions · 13 stateful · 2026-04-28 01:31:18 UTC

Parallelism

50/100

Blocked

46%

Avg conflicts / tx

1.21

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #70,981,739  ·  14 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xd49762c9…1359

0x34b655…2a6f

10 touches
10 conflicts

0xf853eb8e…4027

0x34b655…2a6f

10 touches
10 conflicts

0x1b9e654e…0a08

0x34b655…2a6f

8 touches
6 conflicts

0x578e7f66…1b56

0x34b655…2a6f

8 touches
6 conflicts

0x8db1e0f2…2fcf

0x34b655…2a6f

8 touches
6 conflicts

0x908d4442…2c4b

0x34b655…2a6f

8 touches
6 conflicts

0xedb848fe…6534

0x34b655…2a6f

8 touches
6 conflicts

0xc6417de0…2191

0xc8689a…ee79

8 touches
6 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 0xd49762c96f…3b1359

← previous block·next block →recent activity