Block #71,092,526

← previous blocknext block →recent activity

Analyzing

Block #71,092,526

20 transactions · 16 stateful · 2026-04-28 13:49:01 UTC

Parallelism

80/100

Blocked

38%

Avg conflicts / tx

0.4

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #71,092,526  ·  20 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0002

0xb857c1…9be1

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0xc7323b48…fe5d

0xd32edf…ff58

3 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0015

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0018

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0028

0x1b6862…e19c

2 touches
0 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: 0x065c9d28…a9c394

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity