← previous blocknext block →recent activity

Analyzing

Block #71,238,767

26 transactions · 18 stateful · 2026-04-29 06:02:27 UTC

Parallelism

81/100

Blocked

33%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #71,238,767  ·  26 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

0x1c389468…6b0e

0x34b655…2a6f

10 touches
10 conflicts

0x35b65947…44d1

0xc8689a…ee79

6 touches
3 conflicts

0xdf671536…aa02

0x34b655…2a6f

6 touches
3 conflicts

0xec559eb4…4bdd

0x34b655…2a6f

6 touches
3 conflicts

0xf06c2cf5…61bd

0x34b655…2a6f

6 touches
3 conflicts

0xfa2527aa…9dd5

0x34b655…2a6f

6 touches
3 conflicts

0xfadc118d…5d64

0x34b655…2a6f

6 touches
3 conflicts

0x085df2c1…305a

0x34b655…2a6f

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

10 conflicts on slot 0x1c38946843…a16b0e

← previous block·next block →recent activity