Block #70,956,822

← previous blocknext block →recent activity

Analyzing

Block #70,956,822

41 transactions · 31 stateful · 2026-04-27 22:45:13 UTC

Parallelism

73/100

Blocked

52%

Avg conflicts / tx

1.63

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #70,956,822  ·  41 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x1caac309…771f

0xd32edf…ff58

21 touches
55 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x00000000…001e

0x1b6862…e19c

6 touches
3 conflicts

0xcb45d9d6…cb86

0x1b6862…e19c

6 touches
3 conflicts

0x46cb45de…a566

0x188d58…ea8e

4 touches
1 conflict

0x46cb45de…a568

0x188d58…ea8e

4 touches
1 conflict

0x729c91b8…9537

0x188d58…ea8e

4 touches
1 conflict

0x729c91b8…9538

0x188d58…ea8e

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: 0xd32edf66…9fff58

55 conflicts on slot 0x1caac30906…7e771f

← previous block·next block →recent activity