Block #71,743,915

← previous blocknext block →recent activity

Analyzing

Block #71,743,915

10 transactions · 8 stateful · 2026-05-01 14:10:50 UTC

Parallelism

80/100

Blocked

13%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,743,915  ·  10 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

0xc9d66065…b983

0x065c9d…c394

4 touches
1 conflict

0xfb01ee4b…9915

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x5fd27009…630e

0x065c9d…c394

3 touches
1 conflict

0x436ecfdf…a8b9

0x065c9d…c394

3 touches
1 conflict

0x96e2905f…2dc6

0x065c9d…c394

3 touches
1 conflict

0xa8c84e6e…2d60

0x065c9d…c394

3 touches
1 conflict

0x3e4b8d9f…b8a7

0x33663b…4897

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 0xc9d6606515…ffb983

← previous block·next block →recent activity