← previous blocknext block →recent activity

Analyzing

Block #70,862,968

26 transactions · 24 stateful · 2026-04-27 12:20:19 UTC

Parallelism

85/100

Blocked

58%

Avg conflicts / tx

0.88

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #70,862,968  ·  26 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

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0x2a354a63…0515

0x065c9d…c394

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x4ab14837…e1b2

0x2a68ba…90c5

6 touches
3 conflicts

0xe89e1a22…ce49

0x8d66a4…3095

6 touches
3 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

6 touches
3 conflicts

0x01e7b865…6e6e

0x188d58…ea8e

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

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: 0x2a68ba18…8e90c5

6 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity