Block #70,999,440

← previous blocknext block →recent activity

Analyzing

Block #70,999,440

26 transactions · 24 stateful · 2026-04-28 03:29:07 UTC

Parallelism

69/100

Blocked

50%

Avg conflicts / tx

1.5

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #70,999,440  ·  26 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

16 touches
28 conflicts

0x005fb969…2d97

0x34b655…2a6f

10 touches
10 conflicts

0x3254d19b…f714

0x34b655…2a6f

10 touches
10 conflicts

0x3702b140…97ea

0x34b655…2a6f

10 touches
10 conflicts

0x414e9446…4b59

0x34b655…2a6f

10 touches
10 conflicts

0x65e795ca…0320

0x34b655…2a6f

10 touches
10 conflicts

0x8aa1941d…2988

0x34b655…2a6f

10 touches
10 conflicts

0x904fc3c0…00ec

0x34b655…2a6f

10 touches
10 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

28 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity