← previous blocknext block →recent activity

Analyzing

Block #71,089,880

22 transactions · 17 stateful · 2026-04-28 13:31:23 UTC

Parallelism

86/100

Blocked

35%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,089,880  ·  22 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xfe9adccd…c889

0xd32edf…ff58

5 touches
3 conflicts

0xd19f9d56…9330

0x3bd359…433a

4 touches
1 conflict

0x4b268018…02fb

0x34b655…2a6f

4 touches
1 conflict

0xc4611baa…a70a

0x065c9d…c394

3 touches
1 conflict

0x01e7b865…6e6e

0x188d58…ea8e

2 touches
0 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

2 touches
0 conflicts

0x09000000…0007

0x000000…1000

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: 0x34b6552d…112a6f

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity