Block #70,911,013

← previous blocknext block →recent activity

Analyzing

Block #70,911,013

39 transactions · 34 stateful · 2026-04-27 17:40:15 UTC

Parallelism

72/100

Blocked

65%

Avg conflicts / tx

1.46

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #70,911,013  ·  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

0x60f7fbaf…bd58

0x34b655…2a6f

14 touches
21 conflicts

0x82df902b…760e

0xd32edf…ff58

11 touches
15 conflicts

0x25de453d…9573

0x34b655…2a6f

10 touches
10 conflicts

0x3b3a5945…10d0

0x34b655…2a6f

10 touches
10 conflicts

0xac2a0273…721b

0x34b655…2a6f

10 touches
10 conflicts

0x2484cc15…5afc

0x34b655…2a6f

10 touches
10 conflicts

0x664bf99e…0a8c

0x34b655…2a6f

10 touches
10 conflicts

0x7cb2f3fa…4836

0x34b655…2a6f

10 touches
10 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: 0x34b6552d…112a6f

21 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity