Block #71,701,777

← previous blocknext block →recent activity

Analyzing

Block #71,701,777

10 transactions · 10 stateful · 2026-05-01 09:30:10 UTC

Parallelism

80/100

Blocked

20%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,701,777  ·  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

0xe6f3ee49…2cdb

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x41755291…977f

0x065c9d…c394

4 touches
1 conflict

0x0175b7a6…1dbc

0x33663b…4897

2 touches
0 conflicts

0x0175b7a6…1dbe

0x33663b…4897

2 touches
0 conflicts

0x0c89ea7e…13eb

0x33663b…4897

2 touches
0 conflicts

0x0ef1e663…8f2a

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 0xe6f3ee4960…272cdb

← previous block·next block →recent activity