← previous blocknext block →recent activity

Analyzing

Block #70,922,369

19 transactions · 13 stateful · 2026-04-27 18:55:52 UTC

Parallelism

74/100

Blocked

31%

Avg conflicts / tx

0.53

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #70,922,369  ·  19 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

0x92d610a6…9a40

0x2a68ba…90c5

10 touches
10 conflicts

0x6681bcb2…f8da

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x9c386765…977c

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0004

0xd0f8a6…badc

6 touches
3 conflicts

0x601b4496…cf01

0x065c9d…c394

5 touches
3 conflicts

0x11b69a7e…334e

0xee8c0e…1242

4 touches
1 conflict

0x24968e6d…0132

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: 0x2a68ba18…8e90c5

10 conflicts on slot 0x92d610a6f9…379a40

← previous block·next block →recent activity