← previous blocknext block →recent activity

Analyzing

Block #71,070,871

10 transactions · 8 stateful · 2026-04-28 11:24:42 UTC

Parallelism

70/100

Blocked

38%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,070,871  ·  10 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0x00000000…003d

0x131a2e…0da9

4 touches
1 conflict

0x4ab14837…e1b2

0x2a68ba…90c5

4 touches
1 conflict

0x47b807a2…3307

0x131a2e…0da9

3 touches
1 conflict

0x1746c8e0…52e6

0x065c9d…c394

2 touches
0 conflicts

0x6c88bfef…c23c

0x065c9d…c394

2 touches
0 conflicts

0xbc326b36…d58d

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity