← previous blocknext block →recent activity

Analyzing

Block #71,089,799

25 transactions · 24 stateful · 2026-04-28 13:30:51 UTC

Parallelism

84/100

Blocked

46%

Avg conflicts / tx

0.84

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #71,089,799  ·  25 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xe8479ebe…a331

0xd32edf…ff58

7 touches
6 conflicts

0xfe2bac2b…2cec

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x131a2e…0da9

6 touches
3 conflicts

0xfe2bac2b…2cec

0x131a2e…0da9

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x4ab14837…e1b2

0x2a68ba…90c5

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

6 conflicts on slot 0xe8479ebe32…22a331

← previous block·next block →recent activity