Block #70,911,563

← previous blocknext block →recent activity

Analyzing

Block #70,911,563

18 transactions · 15 stateful · 2026-04-27 17:43:55 UTC

Parallelism

83/100

Blocked

13%

Avg conflicts / tx

0.28

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #70,911,563  ·  18 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

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xbbee74c2…567a

0x065c9d…c394

4 touches
1 conflict

0x24968e6d…0132

0x065c9d…c394

2 touches
0 conflicts

0x438cf5f6…f077

0x2a68ba…90c5

2 touches
0 conflicts

0x2af5f63a…b7b9

0x2e3234…7d90

2 touches
0 conflicts

0x8956cb26…42f7

0x73ada1…8be0

2 touches
0 conflicts

0x8956cb26…42fa

0x73ada1…8be0

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity