← previous blocknext block →recent activity

Analyzing

Block #71,089,806

32 transactions · 27 stateful · 2026-04-28 13:30:54 UTC

Parallelism

81/100

Blocked

52%

Avg conflicts / tx

1.03

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #71,089,806  ·  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

0x27b0d8a3…9c87

0xd32edf…ff58

11 touches
15 conflicts

0x801a6e57…d85c

0x34b655…2a6f

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x00000000…0018

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x6af306bb…2e81

0x3bd359…433a

6 touches
3 conflicts

0xce8bbe33…b72e

0x3bd359…433a

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

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: 0xd32edf66…9fff58

15 conflicts on slot 0x27b0d8a3d4…4b9c87

← previous block·next block →recent activity