Block #70,892,064

← previous blocknext block →recent activity

Analyzing

Block #70,892,064

43 transactions · 29 stateful · 2026-04-27 15:34:02 UTC

Parallelism

79/100

Blocked

55%

Avg conflicts / tx

0.95

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #70,892,064  ·  43 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x60f7fbaf…bd58

0x34b655…2a6f

12 touches
15 conflicts

0x7b7bcac3…8fbf

0x34b655…2a6f

10 touches
10 conflicts

0x1c913164…5c2e

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…0002

0xb857c1…9be1

8 touches
6 conflicts

0x0520da1d…c88e

0x34b655…2a6f

8 touches
6 conflicts

0x3254d19b…f714

0x34b655…2a6f

8 touches
6 conflicts

0x414e9446…4b59

0x34b655…2a6f

8 touches
6 conflicts

0x53b4ef2b…8a05

0x34b655…2a6f

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

15 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity