← previous blocknext block →recent activity

Analyzing

Block #71,289,691

23 transactions · 17 stateful · 2026-04-29 11:41:21 UTC

Parallelism

83/100

Blocked

24%

Avg conflicts / tx

0.39

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #71,289,691  ·  23 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

0x6247a6c3…31b4

0xd32edf…ff58

7 touches
6 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

6 touches
3 conflicts

0xcb45d9d6…cb84

0x1b6862…e19c

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x00000000…001c

0x1b6862…e19c

4 touches
1 conflict

0xfe2bac2b…2cec

0x065c9d…c394

4 touches
1 conflict

0x7764050c…fb67

0x065c9d…c394

3 touches
1 conflict

0x7019e67c…9457

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

6 conflicts on slot 0x6247a6c3eb…8331b4

← previous block·next block →recent activity