Block #70,908,447

← previous blocknext block →recent activity

Analyzing

Block #70,908,447

21 transactions · 17 stateful · 2026-04-27 17:23:10 UTC

Parallelism

81/100

Blocked

29%

Avg conflicts / tx

0.38

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #70,908,447  ·  21 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

0xfe3d37ee…6e67

0x34b655…2a6f

6 touches
3 conflicts

0x35b65947…44d1

0xc8689a…ee79

6 touches
3 conflicts

0x3254d19b…f714

0x34b655…2a6f

6 touches
3 conflicts

0x17e2d2a0…359e

0x34b655…2a6f

6 touches
3 conflicts

0x414e9446…4b59

0x34b655…2a6f

6 touches
3 conflicts

0x53b4ef2b…8a05

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

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