Block #71,090,066

← previous blocknext block →recent activity

Analyzing

Block #71,090,066

35 transactions · 29 stateful · 2026-04-28 13:32:38 UTC

Parallelism

80/100

Blocked

45%

Avg conflicts / tx

0.77

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #71,090,066  ·  35 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0xfe2bac2b…2cec

0x065c9d…c394

8 touches
6 conflicts

0xfbd2f3cd…0087

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…003d

0x131a2e…0da9

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x35801c67…bcbe

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0002

0xb857c1…9be1

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: 0x2a68ba18…8e90c5

6 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity