Block #70,996,670

← previous blocknext block →recent activity

Analyzing

Block #70,996,670

11 transactions · 11 stateful · 2026-04-28 03:10:45 UTC

Parallelism

73/100

Blocked

18%

Avg conflicts / tx

0.27

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #70,996,670  ·  11 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

0x284648f6…8d5c

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0004

0xd0f8a6…badc

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xa9ecf026…3b44

0x065c9d…c394

6 touches
3 conflicts

0x3258ac13…a315

0x065c9d…c394

6 touches
3 conflicts

0x6364bde1…1038

0x065c9d…c394

6 touches
3 conflicts

0xba948623…896e

0x065c9d…c394

5 touches
3 conflicts

0x01a89030…f786

0x98dc6e…8633

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 0x284648f654…528d5c

← previous block·next block →recent activity