Block #70,862,622

← previous blocknext block →recent activity

Analyzing

Block #70,862,622

26 transactions · 21 stateful · 2026-04-27 12:18:01 UTC

Parallelism

65/100

Blocked

57%

Avg conflicts / tx

1.58

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #70,862,622  ·  26 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x6cfafd8b…fdbb

0xd32edf…ff58

17 touches
36 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x2bbc0cfb…c2bf

0x1b6862…e19c

6 touches
3 conflicts

0x41335ddf…94b9

0x34b655…2a6f

6 touches
3 conflicts

0xd984a5e4…5cfc

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001c

0x1b6862…e19c

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

36 conflicts on slot 0x6cfafd8bf3…33fdbb

← previous block·next block →recent activity