Block #71,065,241

← previous blocknext block →recent activity

Analyzing

Block #71,065,241

12 transactions · 11 stateful · 2026-04-28 10:47:08 UTC

Parallelism

83/100

Blocked

9%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,065,241  ·  12 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x5ff9e831…6008

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x3e38b5c9…7b77

0x065c9d…c394

3 touches
1 conflict

0x10b5ff2e…ea9b

0x065c9d…c394

2 touches
0 conflicts

0x89c4b4d5…1ccb

0x065c9d…c394

2 touches
0 conflicts

0xa62a7aef…ee84

0x065c9d…c394

2 touches
0 conflicts

0xa791b18e…7a7b

0x065c9d…c394

2 touches
0 conflicts

0xb17ed949…fec4

0x065c9d…c394

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: 0x065c9d28…a9c394

1 conflict on slot 0x5ff9e83175…0f6008

← previous block·next block →recent activity