← previous blocknext block →recent activity

Analyzing

Block #70,994,900

14 transactions · 13 stateful · 2026-04-28 02:58:58 UTC

Parallelism

71/100

Blocked

38%

Avg conflicts / tx

0.57

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #70,994,900  ·  14 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

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0xf853eb8e…4027

0x34b655…2a6f

6 touches
3 conflicts

0x1c913164…5c2e

0x34b655…2a6f

6 touches
3 conflicts

0xc6417de0…2191

0xc8689a…ee79

6 touches
3 conflicts

0x23951077…539b

0x34b655…2a6f

6 touches
3 conflicts

0x313f2565…5b00

0x34b655…2a6f

6 touches
3 conflicts

0x3638e1ad…ec0e

0x34b655…2a6f

6 touches
3 conflicts

0x5728edaf…f1d4

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 0x60f7fbaf90…97bd58

← previous block·next block →recent activity