Block #70,995,170

← previous blocknext block →recent activity

Analyzing

Block #70,995,170

9 transactions · 8 stateful · 2026-04-28 03:00:46 UTC

Parallelism

56/100

Blocked

38%

Avg conflicts / tx

0.44

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #70,995,170  ·  9 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

0x5c8c6ab6…dc36

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x34bb851e…8cac

0x065c9d…c394

3 touches
1 conflict

0x6a1090d1…1894

0x065c9d…c394

3 touches
1 conflict

0x0498598a…a8f2

0x065c9d…c394

2 touches
1 conflict

0x22f29801…3ad8

0x065c9d…c394

2 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 0x5c8c6ab6f0…86dc36

← previous block·next block →recent activity