← previous blocknext block →recent activity

Analyzing

Block #70,922,411

24 transactions · 20 stateful · 2026-04-27 18:56:09 UTC

Parallelism

79/100

Blocked

25%

Avg conflicts / tx

0.46

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #70,922,411  ·  24 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

0xcf9c3b14…04c8

0xd32edf…ff58

9 touches
10 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0x0b2ed514…d8d7

0x065c9d…c394

3 touches
1 conflict

0x01e7b865…6e6d

0x188d58…ea8e

2 touches
0 conflicts

0x01e7b865…6e6e

0x188d58…ea8e

2 touches
0 conflicts

0x2af5f63a…b7b9

0x2e3234…7d90

2 touches
0 conflicts

0x34e929c7…9e30

0x73ada1…8be0

2 touches
0 conflicts

0x6d735fff…67ff

0x73ada1…8be0

2 touches
0 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 0xcf9c3b147e…3d04c8

← previous block·next block →recent activity