Block #71,090,126

← previous blocknext block →recent activity

Analyzing

Block #71,090,126

38 transactions · 30 stateful · 2026-04-28 13:33:02 UTC

Parallelism

76/100

Blocked

53%

Avg conflicts / tx

1.26

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #71,090,126  ·  38 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x24a3052f…c88e

0xd32edf…ff58

17 touches
36 conflicts

0x47b807a2…3307

0x065c9d…c394

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0xefcdb297…47d0

0x065c9d…c394

5 touches
3 conflicts

0x01e7b865…6e6f

0x188d58…ea8e

4 touches
1 conflict

0xc3c8642a…7da5

0x2a68ba…90c5

4 touches
1 conflict

0x016bd8f2…c85a

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

36 conflicts on slot 0x24a3052f55…a3c88e

← previous block·next block →recent activity