Block #70,956,212

← previous blocknext block →recent activity

Analyzing

Block #70,956,212

11 transactions · 10 stateful · 2026-04-27 22:41:09 UTC

Parallelism

64/100

Blocked

40%

Avg conflicts / tx

0.55

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #70,956,212  ·  11 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

0xe81cfcc6…e4f8

0x065c9d…c394

6 touches
3 conflicts

0x4225f59c…bbd7

0x065c9d…c394

5 touches
3 conflicts

0x9eae9b7f…4814

0x065c9d…c394

4 touches
1 conflict

0xd92f5394…bede

0x065c9d…c394

4 touches
1 conflict

0xfcbd35fc…04cc

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity