← previous blocknext block →recent activity

Analyzing

Block #71,238,746

25 transactions · 23 stateful · 2026-04-29 06:02:19 UTC

Parallelism

76/100

Blocked

48%

Avg conflicts / tx

0.96

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #71,238,746  ·  25 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

12 touches
15 conflicts

0x35b65947…44d1

0xc8689a…ee79

10 touches
10 conflicts

0x53b4ef2b…8a05

0x34b655…2a6f

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0xd32f8498…be67

0x34b655…2a6f

10 touches
10 conflicts

0xdf671536…aa02

0x34b655…2a6f

10 touches
10 conflicts

0xf06c2cf5…61bd

0x34b655…2a6f

10 touches
10 conflicts

0xfa2527aa…9dd5

0x34b655…2a6f

10 touches
10 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

15 conflicts on slot 0x1c38946843…a16b0e

← previous block·next block →recent activity