Block #70,911,031

← previous blocknext block →recent activity

Analyzing

Block #70,911,031

16 transactions · 14 stateful · 2026-04-27 17:40:22 UTC

Parallelism

69/100

Blocked

29%

Avg conflicts / tx

0.63

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #70,911,031  ·  16 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x92d610a6…9a40

0x2a68ba…90c5

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x2193a9bb…ca19

0x065c9d…c394

5 touches
3 conflicts

0xe4d3b9e1…311a

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xbbee74c2…567a

0x065c9d…c394

4 touches
1 conflict

0xed51bae6…2f93

0x065c9d…c394

3 touches
1 conflict

0x17b53d7a…1c4d

0x188d58…ea8e

2 touches
0 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: 0x2a68ba18…8e90c5

6 conflicts on slot 0x92d610a6f9…379a40

← previous block·next block →recent activity