Block #71,289,506

← previous blocknext block →recent activity

Analyzing

Block #71,289,506

10 transactions · 9 stateful · 2026-04-29 11:40:07 UTC

Parallelism

80/100

Blocked

11%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,289,506  ·  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

0x1cc64471…a9de

0x065c9d…c394

4 touches
1 conflict

0x687d1ce0…0f0c

0x065c9d…c394

3 touches
1 conflict

0x7bd71d6e…e052

0x065c9d…c394

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x3b033eb0…f630

0x065c9d…c394

2 touches
0 conflicts

0xc4e2c8a5…7633

0x065c9d…c394

2 touches
0 conflicts

0xf3d7a307…4d63

0x065c9d…c394

2 touches
0 conflicts

0xfe2bac2b…2cec

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 0x1cc6447118…2fa9de

← previous block·next block →recent activity