← previous blocknext block →recent activity

Analyzing

Block #70,922,443

20 transactions · 15 stateful · 2026-04-27 18:56:22 UTC

Parallelism

70/100

Blocked

53%

Avg conflicts / tx

0.85

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #70,922,443  ·  20 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x833e7b57…a80c

0xd32edf…ff58

9 touches
10 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

8 touches
6 conflicts

0xabf82139…717c

0x065c9d…c394

7 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0xc2a59c97…1ef4

0x065c9d…c394

4 touches
1 conflict

0xd2cb2fce…bb67

0x065c9d…c394

3 touches
1 conflict

0x186f544e…8883

0x065c9d…c394

3 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

10 conflicts on slot 0x833e7b57a1…50a80c

← previous block·next block →recent activity