← previous blocknext block →recent activity

Analyzing

Block #70,982,187

34 transactions · 29 stateful · 2026-04-28 01:34:17 UTC

Parallelism

88/100

Blocked

38%

Avg conflicts / tx

0.44

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #70,982,187  ·  34 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

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x09beabbc…065c

0x188d58…ea8e

6 touches
3 conflicts

0x09beabbc…065d

0x188d58…ea8e

6 touches
3 conflicts

0xbbee74c2…567a

0x065c9d…c394

6 touches
3 conflicts

0x4ab14837…e1b2

0x2a68ba…90c5

6 touches
3 conflicts

0x6af306bb…2e81

0x3bd359…433a

4 touches
1 conflict

0xce8bbe33…b72e

0x3bd359…433a

4 touches
1 conflict

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: 0x754704bc…afb603

3 conflicts on slot 0x17606ba612…ea1b6e

← previous block·next block →recent activity