Block #70,892,060

← previous blocknext block →recent activity

Analyzing

Block #70,892,060

26 transactions · 20 stateful · 2026-04-27 15:34:01 UTC

Parallelism

69/100

Blocked

45%

Avg conflicts / tx

1.42

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #70,892,060  ·  26 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

0xd98b3c10…67b8

0x34b655…2a6f

16 touches
28 conflicts

0x1c913164…5c2e

0x34b655…2a6f

8 touches
6 conflicts

0x8a35acfb…d1b0

0x8d66a4…3095

6 touches
3 conflicts

0xb6818fd3…c885

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x7170c140…36bc

0x34b655…2a6f

6 touches
3 conflicts

0x214dc988…ba27

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

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

28 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity