← previous blocknext block →recent activity

Analyzing

Block #71,089,885

26 transactions · 19 stateful · 2026-04-28 13:31:25 UTC

Parallelism

77/100

Blocked

47%

Avg conflicts / tx

0.69

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

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

0x83e43364…f9b4

0xd32edf…ff58

9 touches
10 conflicts

0x801a6e57…d85c

0x34b655…2a6f

6 touches
3 conflicts

0xd025d7d7…f05a

0x3bd359…433a

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0xd53220ed…4734

0x1b6862…e19c

4 touches
1 conflict

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0x085df2c1…305a

0x34b655…2a6f

4 touches
1 conflict

0x11f25e19…8bb1

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

10 conflicts on slot 0x83e4336465…abf9b4

← previous block·next block →recent activity