Block #70,892,332

← previous blocknext block →recent activity

Analyzing

Block #70,892,332

13 transactions · 13 stateful · 2026-04-27 15:35:50 UTC

Parallelism

85/100

Blocked

8%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0x51439a0d…d9b1

0x065c9d…c394

4 touches
1 conflict

0x6db26c98…66f9

0x065c9d…c394

4 touches
1 conflict

0x8491e644…7976

0x065c9d…c394

4 touches
1 conflict

0xeed66bee…4638

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x00000000…001c

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…002c

0x1b6862…e19c

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 0x51439a0d01…4fd9b1

← previous block·next block →recent activity