Block #71,448,811

← previous blocknext block →recent activity

Analyzing

Block #71,448,811

6 transactions · 6 stateful · 2026-04-30 05:22:04 UTC

Parallelism

67/100

Blocked

33%

Avg conflicts / tx

0.33

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,448,811  ·  6 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xa4e3b3b1…0911

0x2a68ba…90c5

4 touches
1 conflict

0x40125f82…4464

0x065c9d…c394

3 touches
1 conflict

0x1e361cb8…3ed8

0xa6afd3…d132

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x70ed4cbb…7714

0x065c9d…c394

2 touches
0 conflicts

0x71ae39dd…a296

0x065c9d…c394

2 touches
0 conflicts

0x9b34cc08…6297

0x065c9d…c394

2 touches
0 conflicts

0x00f7e3b7…e015

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

1 conflict on slot 0xa4e3b3b1bb…130911

← previous block·next block →recent activity