Block #70,892,240

← previous blocknext block →recent activity

Analyzing

Block #70,892,240

31 transactions · 26 stateful · 2026-04-27 15:35:13 UTC

Parallelism

77/100

Blocked

46%

Avg conflicts / tx

0.94

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #70,892,240  ·  31 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xbcfa6fe8…4913

0xd32edf…ff58

13 touches
21 conflicts

0x35801c67…bcc2

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xe75ce681…ba5f

0x188d58…ea8e

4 touches
1 conflict

0xe75ce681…ba61

0x188d58…ea8e

4 touches
1 conflict

0x00000000…0012

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

21 conflicts on slot 0xbcfa6fe802…6c4913

← previous block·next block →recent activity