Block #71,090,122

← previous blocknext block →recent activity

Analyzing

Block #71,090,122

12 transactions · 11 stateful · 2026-04-28 13:33:00 UTC

Parallelism

58/100

Blocked

36%

Avg conflicts / tx

0.58

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #71,090,122  ·  12 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x73cc5b60…fc05

0xd32edf…ff58

7 touches
6 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x535b701d…1e27

0x065c9d…c394

2 touches
0 conflicts

0x616b38fa…c14a

0x065c9d…c394

2 touches
0 conflicts

0x09beabbc…065c

0x188d58…ea8e

2 touches
0 conflicts

0x729c91b8…9537

0x188d58…ea8e

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 0x73cc5b6069…36fc05

← previous block·next block →recent activity