Block #70,892,086

← previous blocknext block →recent activity

Analyzing

Block #70,892,086

11 transactions · 9 stateful · 2026-04-27 15:34:11 UTC

Parallelism

73/100

Blocked

33%

Avg conflicts / tx

0.27

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #70,892,086  ·  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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x1bfe4191…e29b

0x065c9d…c394

4 touches
1 conflict

0x66bf8457…9c07

0x065c9d…c394

4 touches
1 conflict

0xbdd2fd9f…5e4c

0x065c9d…c394

4 touches
1 conflict

0xdfae8a8f…f038

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x95819783…d086

0x065c9d…c394

3 touches
1 conflict

0x34b8f2f2…aa7d

0xd32edf…ff58

3 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

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity