Block #70,862,177

← previous blocknext block →recent activity

Analyzing

Block #70,862,177

18 transactions · 17 stateful · 2026-04-27 12:15:03 UTC

Parallelism

83/100

Blocked

35%

Avg conflicts / tx

0.56

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #70,862,177  ·  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

0x4ab14837…e1b2

0x2a68ba…90c5

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x8e66da19…66b6

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0001

0xc1a578…8e1a

4 touches
1 conflict

0x00000000…003d

0x131a2e…0da9

4 touches
1 conflict

0x4cb2b152…2e00

0x131a2e…0da9

4 touches
1 conflict

0x8e66da19…66b6

0x131a2e…0da9

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

3 conflicts on slot 0x4ab14837eb…ffe1b2

← previous block·next block →recent activity