Block #70,892,247

← previous blocknext block →recent activity

Analyzing

Block #70,892,247

34 transactions · 28 stateful · 2026-04-27 15:35:16 UTC

Parallelism

76/100

Blocked

61%

Avg conflicts / tx

1.18

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #70,892,247  ·  34 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x1c913164…5c2e

0x34b655…2a6f

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0xb6818fd3…c885

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x8a35acfb…d1b0

0x8d66a4…3095

8 touches
6 conflicts

0xaa3492db…3703

0x34b655…2a6f

8 touches
6 conflicts

0xc3aacf13…6b3d

0x34b655…2a6f

6 touches
3 conflicts

0xd49762c9…1359

0x34b655…2a6f

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

10 conflicts on slot 0x1c913164f5…845c2e

← previous block·next block →recent activity