Block #70,911,586

← previous blocknext block →recent activity

Analyzing

Block #70,911,586

33 transactions · 27 stateful · 2026-04-27 17:44:04 UTC

Parallelism

79/100

Blocked

56%

Avg conflicts / tx

1.18

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #70,911,586  ·  33 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xb1ddf077…f6f3

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…0002

0xb857c1…9be1

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0x8a35acfb…d1b0

0x8d66a4…3095

6 touches
3 conflicts

0x00000000…003d

0x131a2e…0da9

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x462c8be7…4f83

0x8d66a4…3095

4 touches
1 conflict

0x5ba51e87…44ee

0x8d66a4…3095

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: 0xd32edf66…9fff58

21 conflicts on slot 0xb1ddf0772a…dcf6f3

← previous block·next block →recent activity