Block #70,995,241

← previous blocknext block →recent activity

Analyzing

Block #70,995,241

14 transactions · 11 stateful · 2026-04-28 03:01:14 UTC

Parallelism

43/100

Blocked

64%

Avg conflicts / tx

2

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #70,995,241  ·  14 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x36be57f1…6c1f

0xd32edf…ff58

15 touches
28 conflicts

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001e

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002e

0x1b6862…e19c

4 touches
1 conflict

0xd53220ed…473a

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

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

28 conflicts on slot 0x36be57f138…2d6c1f

← previous block·next block →recent activity