← previous blocknext block →recent activity

Analyzing

Block #70,951,181

28 transactions · 24 stateful · 2026-04-27 22:07:39 UTC

Parallelism

79/100

Blocked

54%

Avg conflicts / tx

0.64

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #70,951,181  ·  28 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0xadac4a86…c2bc

0x34b655…2a6f

8 touches
6 conflicts

0x35b65947…44d1

0xc8689a…ee79

6 touches
3 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

6 touches
3 conflicts

0x8da71894…b2d3

0x34b655…2a6f

6 touches
3 conflicts

0x97b6fa7b…0d6a

0x34b655…2a6f

6 touches
3 conflicts

0xb138d087…4689

0x34b655…2a6f

6 touches
3 conflicts

0xb245fe36…d765

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 0xea02471df2…601542

← previous block·next block →recent activity