Block #70,892,289

← previous blocknext block →recent activity

Analyzing

Block #70,892,289

14 transactions · 12 stateful · 2026-04-27 15:35:33 UTC

Parallelism

64/100

Blocked

42%

Avg conflicts / tx

0.86

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #70,892,289  ·  14 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0x00000000…0004

0xd0f8a6…badc

8 touches
6 conflicts

0xf823e97f…2ee6

0x065c9d…c394

8 touches
6 conflicts

0xeed66bee…4638

0x065c9d…c394

4 touches
3 conflicts

0x3f99e7de…73f3

0x065c9d…c394

4 touches
3 conflicts

0x51439a0d…d9b1

0x065c9d…c394

4 touches
3 conflicts

0x489ea452…a633

0x065c9d…c394

4 touches
2 conflicts

0xcf3283ba…c9fa

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

10 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity