Block #71,696,685

← previous blocknext block →recent activity

Analyzing

Block #71,696,685

39 transactions · 26 stateful · 2026-05-01 08:56:20 UTC

Parallelism

80/100

Blocked

50%

Avg conflicts / tx

0.9

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #71,696,685  ·  39 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x619aeb91…9cbd

0xd32edf…ff58

15 touches
28 conflicts

0xd74d5bed…5e7e

0x2a68ba…90c5

6 touches
3 conflicts

0x489cb750…7069

0x065c9d…c394

4 touches
1 conflict

0x4cb2b152…2e00

0x065c9d…c394

4 touches
1 conflict

0xcb45d9d6…cb84

0x1b6862…e19c

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xd025d7d7…f05a

0x3bd359…433a

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

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: 0xd32edf66…9fff58

28 conflicts on slot 0x619aeb9132…809cbd

← previous block·next block →recent activity