Block #71,243,728

← previous blocknext block →recent activity

Analyzing

Block #71,243,728

36 transactions · 35 stateful · 2026-04-29 06:35:28 UTC

Parallelism

72/100

Blocked

60%

Avg conflicts / tx

1.97

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #71,243,728  ·  36 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x60f7fbaf…bd58

0x34b655…2a6f

20 touches
45 conflicts

0x00000000…0002

0xb857c1…9be1

10 touches
10 conflicts

0x1c389468…6b0e

0x34b655…2a6f

10 touches
10 conflicts

0x085df2c1…305a

0x34b655…2a6f

8 touches
6 conflicts

0x3254d19b…f714

0x34b655…2a6f

8 touches
6 conflicts

0x3c35979a…975d

0x34b655…2a6f

8 touches
6 conflicts

0x414e9446…4b59

0x34b655…2a6f

8 touches
6 conflicts

0x53b4ef2b…8a05

0x34b655…2a6f

8 touches
6 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

45 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity