Block #71,041,922

← previous blocknext block →recent activity

Analyzing

Block #71,041,922

11 transactions · 9 stateful · 2026-04-28 08:11:54 UTC

Parallelism

73/100

Blocked

33%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,041,922  ·  11 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x7aaf3612…3cc7

0xd32edf…ff58

5 touches
3 conflicts

0xdb90b0e4…617f

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xac9fc41c…e8bc

0x065c9d…c394

4 touches
1 conflict

0x6f7962c8…8c5c

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x3bc444cc…88da

0x065c9d…c394

4 touches
1 conflict

0x703b861a…cbe3

0x188d58…ea8e

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

3 conflicts on slot 0x7aaf361271…543cc7

← previous block·next block →recent activity