← previous blocknext block →recent activity

Analyzing

Block #71,688,804

9 transactions · 8 stateful · 2026-05-01 08:03:45 UTC

Parallelism

56/100

Blocked

38%

Avg conflicts / tx

0.56

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #71,688,804  ·  9 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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…0015

0x1b6862…e19c

6 touches
3 conflicts

0xf8480e2a…dff2

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x06535d3d…a8e5

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

4 touches
1 conflict

0xa14333f3…6e58

0x065c9d…c394

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: 0x1b68626d…2de19c

3 conflicts on slot 0x0000000000…000015

← previous block·next block →recent activity