Block #71,092,253

← previous blocknext block →recent activity

Analyzing

Block #71,092,253

31 transactions · 27 stateful · 2026-04-28 13:47:12 UTC

Parallelism

84/100

Blocked

56%

Avg conflicts / tx

0.87

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #71,092,253  ·  31 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x8c49c85c…ee96

0x34b655…2a6f

8 touches
6 conflicts

0x4ab14837…e1b2

0x2a68ba…90c5

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x47b807a2…3307

0x131a2e…0da9

6 touches
4 conflicts

0x8a35acfb…d1b0

0x8d66a4…3095

6 touches
3 conflicts

0x5a9c2dc3…43ab

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x47b807a2…3307

0x065c9d…c394

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: 0x34b6552d…112a6f

6 conflicts on slot 0x8c49c85c3e…afee96

← previous block·next block →recent activity