← previous blocknext block →recent activity

Analyzing

Block #70,909,074

16 transactions · 14 stateful · 2026-04-27 17:27:20 UTC

Parallelism

75/100

Blocked

36%

Avg conflicts / tx

0.44

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #70,909,074  ·  16 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

0xb9d2cf20…a668

0x34b655…2a6f

6 touches
3 conflicts

0xbb1747e2…f78b

0x34b655…2a6f

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x4ab14837…e1b2

0x2a68ba…90c5

4 touches
1 conflict

0x085df2c1…305a

0x34b655…2a6f

4 touches
1 conflict

0x1aff276b…6904

0x34b655…2a6f

4 touches
1 conflict

0x35c59534…4246

0x34b655…2a6f

4 touches
1 conflict

0x388f889f…a655

0x34b655…2a6f

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: 0x34b6552d…112a6f

3 conflicts on slot 0xb9d2cf2005…28a668

← previous block·next block →recent activity