Block #70,911,221

← previous blocknext block →recent activity

Analyzing

Block #70,911,221

39 transactions · 33 stateful · 2026-04-27 17:41:38 UTC

Parallelism

72/100

Blocked

55%

Avg conflicts / tx

1.15

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #70,911,221  ·  39 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x900e141a…e01f

0xd32edf…ff58

15 touches
28 conflicts

0xbb1747e2…f78b

0x34b655…2a6f

8 touches
6 conflicts

0x6af306bb…2e81

0x3bd359…433a

6 touches
3 conflicts

0xce8bbe33…b72e

0x3bd359…433a

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0xf91b744e…9117

0x754704…b603

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

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

28 conflicts on slot 0x900e141af4…3ee01f

← previous block·next block →recent activity