Block #70,911,385

← previous blocknext block →recent activity

Analyzing

Block #70,911,385

10 transactions · 10 stateful · 2026-04-27 17:42:44 UTC

Parallelism

70/100

Blocked

20%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #70,911,385  ·  10 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0x00000000…0004

0xd0f8a6…badc

6 touches
3 conflicts

0x429224f0…a818

0x065c9d…c394

6 touches
3 conflicts

0xcfc6cf0d…2e83

0x065c9d…c394

3 touches
1 conflict

0x2688f1ff…3530

0x065c9d…c394

3 touches
1 conflict

0x55849a51…a6ed

0x065c9d…c394

3 touches
1 conflict

0x85a1e393…181d

0x065c9d…c394

3 touches
1 conflict

0xb9684c09…4d2e

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity