Block #71,743,926

← previous blocknext block →recent activity

Analyzing

Block #71,743,926

7 transactions · 7 stateful · 2026-05-01 14:10:55 UTC

Parallelism

71/100

Blocked

14%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0xfb01ee4b…9915

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x4f058c5a…41f7

0x065c9d…c394

3 touches
1 conflict

0x9be1e4a1…5977

0x065c9d…c394

3 touches
1 conflict

0xc3d65fdc…b1a9

0x065c9d…c394

3 touches
1 conflict

0x508387de…c644

0x2a68ba…90c5

2 touches
0 conflicts

0x0175b7a6…1dba

0x33663b…4897

2 touches
0 conflicts

0x0175b7a6…1dbc

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 0xfb01ee4b52…3e9915

← previous block·next block →recent activity