Block #71,092,529

← previous blocknext block →recent activity

Analyzing

Block #71,092,529

23 transactions · 21 stateful · 2026-04-28 13:49:02 UTC

Parallelism

78/100

Blocked

29%

Avg conflicts / tx

0.39

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #71,092,529  ·  23 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

0x1c913164…5c2e

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x999eba07…b27e

0x065c9d…c394

4 touches
1 conflict

0xffaa4bff…c026

0x065c9d…c394

4 touches
1 conflict

0x50059a18…9b7b

0x34b655…2a6f

4 touches
1 conflict

0x55b6a001…1e7a

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x9948dde8…6a26

0x34b655…2a6f

4 touches
1 conflict

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 0x1c913164f5…845c2e

← previous block·next block →recent activity