← previous blocknext block →recent activity

Analyzing

Block #71,288,929

9 transactions · 9 stateful · 2026-04-29 11:36:18 UTC

Parallelism

78/100

Blocked

11%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,288,929  ·  9 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

0xf3d7a307…4d63

0x065c9d…c394

4 touches
1 conflict

0xdb962b83…e6be

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x816da7dd…8587

0x065c9d…c394

3 touches
1 conflict

0xe17c4ce5…f535

0x065c9d…c394

3 touches
1 conflict

0x89daf25c…bc70

0x065c9d…c394

3 touches
1 conflict

0x5786d100…c791

0x065c9d…c394

3 touches
1 conflict

0x00000000…0000

0x81e8ed…9c15

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 0xf3d7a307cc…f14d63

← previous block·next block →recent activity