← previous blocknext block →recent activity

Analyzing

Block #70,910,756

40 transactions · 34 stateful · 2026-04-27 17:38:32 UTC

Parallelism

82/100

Blocked

53%

Avg conflicts / tx

1.02

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #70,910,756  ·  40 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

14 touches
21 conflicts

0xb9d2cf20…a668

0x34b655…2a6f

8 touches
6 conflicts

0x8a35acfb…d1b0

0x8d66a4…3095

8 touches
6 conflicts

0x35c59534…4246

0x34b655…2a6f

6 touches
3 conflicts

0x414e9446…4b59

0x34b655…2a6f

6 touches
3 conflicts

0x5150691f…c7fe

0x34b655…2a6f

6 touches
3 conflicts

0x53b4ef2b…8a05

0x34b655…2a6f

6 touches
3 conflicts

0x904fc3c0…00ec

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

21 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity