← previous blocknext block →recent activity

Analyzing

Block #71,697,213

16 transactions · 12 stateful · 2026-05-01 08:59:49 UTC

Parallelism

81/100

Blocked

25%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,697,213  ·  16 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x801a6e57…d85c

0x34b655…2a6f

6 touches
3 conflicts

0xd6aabe89…92f5

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xfa2527aa…9dd5

0x34b655…2a6f

6 touches
3 conflicts

0x04a837dd…e245

0x34b655…2a6f

6 touches
3 conflicts

0x4e01a6b9…ed8e

0x34b655…2a6f

6 touches
3 conflicts

0xfadc118d…5d64

0x34b655…2a6f

4 touches
1 conflict

0x95eabf72…43f1

0x34b655…2a6f

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: 0x34b6552d…112a6f

3 conflicts on slot 0x801a6e5726…c1d85c

← previous block·next block →recent activity