← previous blocknext block →recent activity

Analyzing

Block #71,243,162

8 transactions · 7 stateful · 2026-04-29 06:31:41 UTC

Parallelism

63/100

Blocked

29%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,243,162  ·  8 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x23bbc51d…668c

0x065c9d…c394

6 touches
3 conflicts

0x499d41bd…0ef3

0x065c9d…c394

6 touches
3 conflicts

0xd3e71746…430f

0x065c9d…c394

6 touches
3 conflicts

0xdf38fee8…9bc4

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0004

0xd0f8a6…badc

6 touches
3 conflicts

0x30837b4d…b103

0x34b655…2a6f

2 touches
0 conflicts

0x552b821c…c190

0x34b655…2a6f

2 touches
0 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: 0x065c9d28…a9c394

3 conflicts on slot 0x23bbc51d31…7e668c

← previous block·next block →recent activity