Block #70,918,176

← previous blocknext block →recent activity

Analyzing

Block #70,918,176

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

Parallelism

75/100

Blocked

57%

Avg conflicts / tx

1.19

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #70,918,176  ·  32 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

0x60f7fbaf…bd58

0x34b655…2a6f

12 touches
15 conflicts

0xbb1747e2…f78b

0x34b655…2a6f

8 touches
6 conflicts

0x24968e6d…0132

0x065c9d…c394

8 touches
6 conflicts

0x8a35acfb…d1b0

0x8d66a4…3095

8 touches
6 conflicts

0x00000000…0001

0xc1a578…8e1a

6 touches
3 conflicts

0xbbee74c2…567a

0x065c9d…c394

6 touches
3 conflicts

0x8a35acfb…d1ae

0x8d66a4…3095

6 touches
3 conflicts

0x8a35acfb…d1af

0x8d66a4…3095

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

15 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity