Block #70,911,168

← previous blocknext block →recent activity

Analyzing

Block #70,911,168

25 transactions · 22 stateful · 2026-04-27 17:41:17 UTC

Parallelism

84/100

Blocked

41%

Avg conflicts / tx

0.6

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #70,911,168  ·  25 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

0xbb1747e2…f78b

0x34b655…2a6f

8 touches
6 conflicts

0x839b8288…9557

0xd32edf…ff58

7 touches
6 conflicts

0x17e2d2a0…359e

0x34b655…2a6f

6 touches
3 conflicts

0x1aff276b…6904

0x34b655…2a6f

6 touches
3 conflicts

0x2877f440…c2c8

0x34b655…2a6f

6 touches
3 conflicts

0x3254d19b…f714

0x34b655…2a6f

6 touches
3 conflicts

0x414e9446…4b59

0x34b655…2a6f

6 touches
3 conflicts

0x53b4ef2b…8a05

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

6 conflicts on slot 0xbb1747e217…82f78b

← previous block·next block →recent activity