Block #70,846,355

← previous blocknext block →recent activity

Analyzing

Block #70,846,355

21 transactions · 18 stateful · 2026-04-27 10:29:37 UTC

Parallelism

81/100

Blocked

22%

Avg conflicts / tx

0.33

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #70,846,355  ·  21 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

6 touches
3 conflicts

0x8e66da19…66b6

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xd984a5e4…5cfc

0x34b655…2a6f

4 touches
1 conflict

0xb9d0fb60…6c9f

0x065c9d…c394

4 touches
1 conflict

0x77101d69…d068

0x065c9d…c394

3 touches
1 conflict

0xa8c9c706…b7ae

0x065c9d…c394

3 touches
1 conflict

0xd5b10148…e634

0x1b6862…e19c

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