Block #71,741,590

← previous blocknext block →recent activity

Analyzing

Block #71,741,590

35 transactions · 20 stateful · 2026-05-01 13:55:20 UTC

Parallelism

91/100

Blocked

40%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,741,590  ·  35 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

0xd025d7d7…f05a

0x3bd359…433a

6 touches
3 conflicts

0xd7e0ebc6…6843

0xd32edf…ff58

5 touches
3 conflicts

0x6af306bb…2e81

0x3bd359…433a

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x1c354dc0…96de

0x754704…b603

4 touches
1 conflict

0xf91b744e…9117

0x754704…b603

4 touches
1 conflict

0x729c91b8…9537

0x188d58…ea8e

4 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: 0x3bd359c1…15433a

3 conflicts on slot 0xd025d7d72f…4df05a

← previous block·next block →recent activity