Block #71,743,966

← previous blocknext block →recent activity

Analyzing

Block #71,743,966

21 transactions · 11 stateful · 2026-05-01 14:11:11 UTC

Parallelism

90/100

Blocked

18%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0ed87692…8bcc

0x065c9d…c394

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0xc4cb5fb2…6a56

0x065c9d…c394

4 touches
1 conflict

0xd8b84487…6efa

0x065c9d…c394

3 touches
1 conflict

0x170db1ea…f223

0x065c9d…c394

3 touches
1 conflict

0x8876d94c…8435

0x2a68ba…90c5

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 0x0000000000…00003d

← previous block·next block →recent activity