Block #70,908,759

← previous blocknext block →recent activity

Analyzing

Block #70,908,759

8 transactions · 8 stateful · 2026-04-27 17:25:14 UTC

Parallelism

50/100

Blocked

38%

Avg conflicts / tx

0.75

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #70,908,759  ·  8 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x00000000…0004

0xd0f8a6…badc

8 touches
6 conflicts

0x1e2bddaa…8ec0

0x065c9d…c394

7 touches
6 conflicts

0x4af6ea26…c71c

0x065c9d…c394

7 touches
6 conflicts

0x52ea0143…c66b

0x065c9d…c394

7 touches
6 conflicts

0xa2a78c06…344a

0x065c9d…c394

6 touches
6 conflicts

0x24968e6d…0132

0x065c9d…c394

4 touches
1 conflict

0xb182240d…dfb4

0x065c9d…c394

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity