← previous blocknext block →recent activity

Analyzing

Block #71,688,819

13 transactions · 9 stateful · 2026-05-01 08:03:51 UTC

Parallelism

85/100

Blocked

11%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,688,819  ·  13 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

0x41755291…977f

0x065c9d…c394

4 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xa8109a3f…e98f

0x065c9d…c394

3 touches
1 conflict

0xb66960af…35b8

0x065c9d…c394

3 touches
1 conflict

0xcd9157f0…47d9

0x065c9d…c394

3 touches
1 conflict

0xdea783ba…ce75

0x065c9d…c394

3 touches
1 conflict

0x885e8cc5…e826

0x065c9d…c394

3 touches
1 conflict

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 0x4175529119…79977f

← previous block·next block →recent activity