← previous blocknext block →recent activity

Analyzing

Block #70,951,160

8 transactions · 8 stateful · 2026-04-27 22:07:31 UTC

Parallelism

75/100

Blocked

13%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,951,160  ·  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

0x1a64fc11…76d7

0x065c9d…c394

4 touches
1 conflict

0xe5174b61…6a0c

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x810a6487…4fa3

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0xbffa4ce2…b90d

0x065c9d…c394

4 touches
1 conflict

0x78273a08…1894

0x065c9d…c394

2 touches
1 conflict

0x97b958d2…aec4

0x065c9d…c394

2 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 0x1a64fc11df…d976d7

← previous block·next block →recent activity