← previous blocknext block →recent activity

Analyzing

Block #70,892,467

21 transactions · 17 stateful · 2026-04-27 15:36:44 UTC

Parallelism

81/100

Blocked

41%

Avg conflicts / tx

0.57

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #70,892,467  ·  21 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x848e5ccd…ad32

0xd32edf…ff58

7 touches
6 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

6 touches
3 conflicts

0xafee3573…354c

0x065c9d…c394

4 touches
1 conflict

0xc53af6f0…50bd

0x34b655…2a6f

4 touches
1 conflict

0x333dc51f…9eda

0x065c9d…c394

4 touches
1 conflict

0x9a555477…19a8

0x754704…b603

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

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: 0xd32edf66…9fff58

6 conflicts on slot 0x848e5ccded…40ad32

← previous block·next block →recent activity