Block #70,892,343

← previous blocknext block →recent activity

Analyzing

Block #70,892,343

8 transactions · 6 stateful · 2026-04-27 15:35:54 UTC

Parallelism

75/100

Blocked

17%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,892,343  ·  8 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x1bfe4191…e29b

0x065c9d…c394

3 touches
1 conflict

0x2f1d9a74…f3fb

0x065c9d…c394

3 touches
1 conflict

0x3f99e7de…73f3

0x065c9d…c394

3 touches
1 conflict

0x6aca9b90…5112

0x065c9d…c394

3 touches
1 conflict

0x94e7f277…471b

0x34b655…2a6f

2 touches
0 conflicts

0xb6598a07…de75

0x34b655…2a6f

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

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity