Block #70,862,753

← previous blocknext block →recent activity

Analyzing

Block #70,862,753

17 transactions · 13 stateful · 2026-04-27 12:18:53 UTC

Parallelism

76/100

Blocked

38%

Avg conflicts / tx

0.47

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #70,862,753  ·  17 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

0x8a35acfb…d1b0

0x8d66a4…3095

6 touches
3 conflicts

0x8a35acfb…d1b1

0x8d66a4…3095

6 touches
3 conflicts

0x2484cc15…5afc

0x34b655…2a6f

4 touches
1 conflict

0x2ae2d13c…2d7b

0x34b655…2a6f

4 touches
1 conflict

0x3df3de0d…cd8b

0x34b655…2a6f

4 touches
1 conflict

0x4897228b…63c5

0x34b655…2a6f

4 touches
1 conflict

0x50c2960c…5f37

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

6 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity