← previous blocknext block →recent activity

Analyzing

Block #71,069,975

16 transactions · 13 stateful · 2026-04-28 11:18:43 UTC

Parallelism

81/100

Blocked

31%

Avg conflicts / tx

0.44

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,069,975  ·  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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xd89f212d…2bbf

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x4ce554a7…53b5

0x065c9d…c394

4 touches
1 conflict

0xa6420d28…6455

0x065c9d…c394

4 touches
1 conflict

0xf04b0222…847a

0x065c9d…c394

4 touches
1 conflict

0x3081b8bd…bba6

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity