Block #70,908,620

← previous blocknext block →recent activity

Analyzing

Block #70,908,620

27 transactions · 24 stateful · 2026-04-27 17:24:19 UTC

Parallelism

78/100

Blocked

33%

Avg conflicts / tx

0.81

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #70,908,620  ·  27 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xc3c8642a…7da5

0x2a68ba…90c5

10 touches
10 conflicts

0xed832e4d…7170

0xd32edf…ff58

9 touches
10 conflicts

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0x00000000…001d

0x1b6862…e19c

6 touches
3 conflicts

0xcb45d9d6…cb85

0x1b6862…e19c

6 touches
3 conflicts

0xaa892038…85af

0x065c9d…c394

5 touches
3 conflicts

0x5f98bd79…f16d

0x065c9d…c394

5 touches
3 conflicts

0x12309510…0ac2

0x000000…012a

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

10 conflicts on slot 0xc3c8642ae9…317da5

← previous block·next block →recent activity