← previous blocknext block →recent activity

Analyzing

Block #71,450,758

16 transactions · 15 stateful · 2026-04-30 05:35:03 UTC

Parallelism

75/100

Blocked

27%

Avg conflicts / tx

0.44

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #71,450,758  ·  16 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

0x57c82d2a…6820

0xd32edf…ff58

7 touches
6 conflicts

0x1c913164…5c2e

0x34b655…2a6f

4 touches
1 conflict

0xa23e4e28…e875

0x34b655…2a6f

4 touches
1 conflict

0x729c91b8…9537

0x188d58…ea8e

2 touches
0 conflicts

0x729c91b8…9538

0x188d58…ea8e

2 touches
0 conflicts

0x08b8e539…b9f9

0x754704…b603

2 touches
0 conflicts

0x17606ba6…1b6e

0x754704…b603

2 touches
0 conflicts

0x1c354dc0…96de

0x754704…b603

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: 0xd32edf66…9fff58

6 conflicts on slot 0x57c82d2ade…cb6820

← previous block·next block →recent activity