Block #71,683,754

← previous blocknext block →recent activity

Analyzing

Block #71,683,754

10 transactions · 7 stateful · 2026-05-01 07:30:11 UTC

Parallelism

80/100

Blocked

14%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,683,754  ·  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

0xb6af401e…b071

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xfc101ae2…f96e

0x065c9d…c394

3 touches
1 conflict

0x0aaa700b…817b

0x065c9d…c394

3 touches
1 conflict

0x6514c42a…439f

0x065c9d…c394

3 touches
1 conflict

0xd5c961f2…7fd5

0x065c9d…c394

2 touches
0 conflicts

0x1a4b4152…0a08

0x33663b…4897

2 touches
0 conflicts

0x2e2214a9…fe0d

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 0xb6af401e53…5ab071

← previous block·next block →recent activity