← previous blocknext block →recent activity

Analyzing

Block #70,917,423

32 transactions · 28 stateful · 2026-04-27 18:22:59 UTC

Parallelism

69/100

Blocked

54%

Avg conflicts / tx

1.13

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #70,917,423  ·  32 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

12 touches
15 conflicts

0xbb1747e2…f78b

0x34b655…2a6f

10 touches
10 conflicts

0x2877f440…c2c8

0x34b655…2a6f

8 touches
6 conflicts

0x3254d19b…f714

0x34b655…2a6f

8 touches
6 conflicts

0x414e9446…4b59

0x34b655…2a6f

8 touches
6 conflicts

0x53b4ef2b…8a05

0x34b655…2a6f

8 touches
6 conflicts

0x6f05961b…ecba

0x34b655…2a6f

8 touches
6 conflicts

0x85a88798…f85e

0x34b655…2a6f

8 touches
6 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

15 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity