← previous blocknext block →recent activity

Analyzing

Block #70,922,370

7 transactions · 7 stateful · 2026-04-27 18:55:53 UTC

Parallelism

71/100

Blocked

14%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,922,370  ·  7 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x24968e6d…0132

0x065c9d…c394

4 touches
1 conflict

0x894cced8…6897

0x065c9d…c394

3 touches
1 conflict

0x92d610a6…9a40

0x2a68ba…90c5

2 touches
0 conflicts

0x968bdacb…f461

0x2a68ba…90c5

2 touches
0 conflicts

0x33e0213d…6400

0x34b655…2a6f

2 touches
0 conflicts

0x8f84702c…c5f9

0x34b655…2a6f

2 touches
0 conflicts

0x94e7f277…471b

0x34b655…2a6f

2 touches
0 conflicts

0xc824469a…6425

0x34b655…2a6f

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: 0x065c9d28…a9c394

1 conflict on slot 0x24968e6db4…f00132

← previous block·next block →recent activity