Block #71,696,678

← previous blocknext block →recent activity

Analyzing

Block #71,696,678

19 transactions · 14 stateful · 2026-05-01 08:56:17 UTC

Parallelism

68/100

Blocked

43%

Avg conflicts / tx

0.79

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #71,696,678  ·  19 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x92d610a6…9a40

0x2a68ba…90c5

10 touches
10 conflicts

0xc4c78918…f7bf

0x065c9d…c394

9 touches
10 conflicts

0x182847de…4946

0xd32edf…ff58

7 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x00000000…0003

0x094452…0a09

4 touches
1 conflict

0x00000000…0004

0x094452…0a09

4 touches
1 conflict

0x09beabbc…065c

0x188d58…ea8e

4 touches
1 conflict

0x09beabbc…065d

0x188d58…ea8e

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: 0x2a68ba18…8e90c5

10 conflicts on slot 0x92d610a6f9…379a40

← previous block·next block →recent activity