← previous blocknext block →recent activity

Analyzing

Block #70,892,464

37 transactions · 31 stateful · 2026-04-27 15:36:42 UTC

Parallelism

84/100

Blocked

58%

Avg conflicts / tx

0.97

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #70,892,464  ·  37 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xf1e99f9c…deb0

0xd32edf…ff58

9 touches
10 conflicts

0xcf3283ba…c9fa

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x7b7bcac3…8fbf

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001c

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002c

0x1b6862…e19c

6 touches
3 conflicts

0x3bd55803…5d4c

0x1b6862…e19c

6 touches
3 conflicts

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 0xf1e99f9c25…badeb0

← previous block·next block →recent activity