Block #70,381,270

← previous blocknext block →recent activity

Analyzing

Block #70,381,270

10 transactions · 9 stateful · 2026-04-25 06:52:02 UTC

Parallelism

60/100

Blocked

33%

Avg conflicts / tx

0.4

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #70,381,270  ·  10 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

0x0764eb12…63a9

0x065c9d…c394

4 touches
1 conflict

0x2ddcfa6d…a5dc

0x065c9d…c394

4 touches
1 conflict

0x3a8662b0…dcdc

0x065c9d…c394

4 touches
1 conflict

0x5e3242d2…ab1e

0x065c9d…c394

4 touches
1 conflict

0x70df89fb…772d

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