← previous blocknext block →recent activity

Analyzing

Block #71,041,759

32 transactions · 29 stateful · 2026-04-28 08:10:49 UTC

Parallelism

81/100

Blocked

52%

Avg conflicts / tx

1.06

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #71,041,759  ·  32 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

0xa02838a3…bc54

0x34b655…2a6f

10 touches
10 conflicts

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0xfd1e5e21…cfda

0xd32edf…ff58

7 touches
6 conflicts

0x941a33ca…2f92

0xd18b7e…414b

6 touches
3 conflicts

0xf26eda05…0203

0xd18b7e…414b

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xd4ef1f4f…cffb

0x34b655…2a6f

6 touches
3 conflicts

0x6af306bb…2e81

0x3bd359…433a

6 touches
3 conflicts

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

10 conflicts on slot 0xa02838a385…ffbc54

← previous block·next block →recent activity