Block #71,696,783

← previous blocknext block →recent activity

Analyzing

Block #71,696,783

8 transactions · 8 stateful · 2026-05-01 08:57:00 UTC

Parallelism

75/100

Blocked

13%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,696,783  ·  8 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

0xabe44c5a…1d8e

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x1ec9e06c…6d58

0x065c9d…c394

4 touches
1 conflict

0xe92b42bf…6008

0x065c9d…c394

3 touches
1 conflict

0x6605d909…f4e6

0x065c9d…c394

3 touches
1 conflict

0x1075f6bb…3592

0x065c9d…c394

3 touches
1 conflict

0x1a8c5059…fb00

0x065c9d…c394

3 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

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 0xabe44c5a3c…381d8e

← previous block·next block →recent activity