Block #71,702,081

← previous blocknext block →recent activity

Analyzing

Block #71,702,081

15 transactions · 12 stateful · 2026-05-01 09:32:11 UTC

Parallelism

87/100

Blocked

8%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,702,081  ·  15 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

0x2df045f1…2bbc

0x065c9d…c394

4 touches
1 conflict

0x86d80ecb…db3b

0x065c9d…c394

3 touches
1 conflict

0xabe065a2…477c

0x065c9d…c394

3 touches
1 conflict

0xd2a4936c…e2c7

0x065c9d…c394

3 touches
1 conflict

0xab2f6eed…254a

0x188d58…ea8e

2 touches
0 conflicts

0xab2f6eed…254b

0x188d58…ea8e

2 touches
0 conflicts

0x30d9a412…e84b

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