← previous blocknext block →recent activity

Analyzing

Block #71,089,709

34 transactions · 28 stateful · 2026-04-28 13:30:15 UTC

Parallelism

76/100

Blocked

46%

Avg conflicts / tx

0.74

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #71,089,709  ·  34 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xd9f18d9a…141d

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0012

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0018

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0028

0x1b6862…e19c

10 touches
10 conflicts

0x65bd5770…5eca

0x1b6862…e19c

10 touches
10 conflicts

0xe850071e…6d10

0xd32edf…ff58

9 touches
10 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: 0x1b68626d…2de19c

10 conflicts on slot 0xd9f18d9a4a…7f141d

← previous block·next block →recent activity