Block #70,956,544

← previous blocknext block →recent activity

Analyzing

Block #70,956,544

9 transactions · 8 stateful · 2026-04-27 22:43:22 UTC

Parallelism

56/100

Blocked

38%

Avg conflicts / tx

0.67

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

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

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xfe1ed1ae…c0e0

0x065c9d…c394

8 touches
6 conflicts

0x00000000…0004

0xd0f8a6…badc

8 touches
6 conflicts

0x00b17183…36d9

0x065c9d…c394

6 touches
4 conflicts

0x4df69c2e…5e9f

0x065c9d…c394

6 touches
4 conflicts

0x9ec1b159…f952

0x065c9d…c394

6 touches
4 conflicts

0x24968e6d…0132

0x065c9d…c394

4 touches
1 conflict

0x683e6f40…f35f

0x065c9d…c394

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity