← previous blocknext block →recent activity

Analyzing

Block #70,922,442

30 transactions · 19 stateful · 2026-04-27 18:56:22 UTC

Parallelism

83/100

Blocked

42%

Avg conflicts / tx

0.57

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #70,922,442  ·  30 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x8ee2ea17…4459

0xd32edf…ff58

9 touches
10 conflicts

0xd40bddc1…773c

0x34b655…2a6f

6 touches
3 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x6a029a5b…c2ad

0x065c9d…c394

5 touches
3 conflicts

0x085df2c1…305a

0x34b655…2a6f

4 touches
1 conflict

0x1b5d2e60…99b5

0x34b655…2a6f

4 touches
1 conflict

0x65e795ca…0320

0x34b655…2a6f

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

10 conflicts on slot 0x8ee2ea17be…d74459

← previous block·next block →recent activity