Block #71,448,845

← previous blocknext block →recent activity

Analyzing

Block #71,448,845

7 transactions · 5 stateful · 2026-04-30 05:22:17 UTC

Parallelism

71/100

Blocked

40%

Avg conflicts / tx

0.29

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,448,845  ·  7 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

0xd79cbec8…7926

0x065c9d…c394

3 touches
1 conflict

0xa8d3e2f0…5e62

0xd32edf…ff58

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x536dd325…f1e6

0x065c9d…c394

2 touches
0 conflicts

0x812b99db…800a

0x065c9d…c394

2 touches
0 conflicts

0xc1d1c3c3…9720

0x065c9d…c394

2 touches
0 conflicts

0xf4e686a5…f5dd

0x065c9d…c394

2 touches
0 conflicts

0x09beabbc…065c

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

1 conflict on slot 0xd79cbec81a…af7926

← previous block·next block →recent activity