← previous blocknext block →recent activity

Analyzing

Block #71,590,335

9 transactions · 8 stateful · 2026-04-30 21:08:26 UTC

Parallelism

78/100

Blocked

13%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,590,335  ·  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

0x42cdb2db…71c7

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x45232a5a…c03a

0x065c9d…c394

3 touches
1 conflict

0x46ebf6bd…8715

0x065c9d…c394

3 touches
1 conflict

0xbe9f1c08…53b5

0x065c9d…c394

3 touches
1 conflict

0xf7be9c71…af68

0x065c9d…c394

2 touches
0 conflicts

0xff3e68fa…7460

0x065c9d…c394

2 touches
0 conflicts

0x1a4b4152…0a08

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 0x42cdb2db6e…3a71c7

← previous block·next block →recent activity