← previous blocknext block →recent activity

Analyzing

Block #70,891,586

35 transactions · 28 stateful · 2026-04-27 15:30:51 UTC

Parallelism

89/100

Blocked

50%

Avg conflicts / tx

0.74

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #70,891,586  ·  35 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0xe6b7c4c5…7e78

0xd32edf…ff58

7 touches
6 conflicts

0xf51c31aa…e42f

0x065c9d…c394

6 touches
3 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x7b7bcac3…8fbf

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0000

0x659bd0…a9da

4 touches
1 conflict

0x00000000…0002

0x659bd0…a9da

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: 0x2a68ba18…8e90c5

6 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity