Block #70,862,358

← previous blocknext block →recent activity

Analyzing

Block #70,862,358

15 transactions · 13 stateful · 2026-04-27 12:16:15 UTC

Parallelism

80/100

Blocked

38%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #70,862,358  ·  15 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

0x00000000…0002

0xb857c1…9be1

6 touches
3 conflicts

0x00bac013…a28c

0xfd44b3…00d1

4 touches
1 conflict

0xe72962f6…e169

0x8d66a4…3095

4 touches
1 conflict

0xe96c91d2…32ff

0x8d66a4…3095

4 touches
1 conflict

0xb6b74ae0…8d5e

0xea1b8e…c5ec

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x462c8be7…4f83

0x8d66a4…3095

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: 0xb857c13a…1a9be1

3 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity