Block #70,891,811

← previous blocknext block →recent activity

Analyzing

Block #70,891,811

25 transactions · 16 stateful · 2026-04-27 15:32:21 UTC

Parallelism

88/100

Blocked

38%

Avg conflicts / tx

0.28

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #70,891,811  ·  25 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x468c69b1…af11

0x8d66a4…3095

6 touches
3 conflicts

0x8a35acfb…d1b0

0x8d66a4…3095

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xe6bc2705…d15b

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x462c8be7…4f83

0x8d66a4…3095

4 touches
1 conflict

0x00000000…0002

0xb857c1…9be1

4 touches
1 conflict

0x60f7fbaf…bd58

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: 0x8d66a43f…113095

3 conflicts on slot 0x468c69b112…86af11

← previous block·next block →recent activity