← previous blocknext block →recent activity

Analyzing

Block #71,289,695

22 transactions · 14 stateful · 2026-04-29 11:41:23 UTC

Parallelism

73/100

Blocked

50%

Avg conflicts / tx

0.86

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #71,289,695  ·  22 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

0xb0f2edf8…4a2d

0xd32edf…ff58

11 touches
15 conflicts

0x5b6476c3…93c9

0x065c9d…c394

6 touches
3 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

6 touches
3 conflicts

0xea02471d…1539

0x34b655…2a6f

4 touches
1 conflict

0x335a161d…fe7f

0x000000…012a

2 touches
0 conflicts

0x00000000…003d

0x122c0d…e3fa

2 touches
0 conflicts

0x2a8c7786…56a2

0x122c0d…e3fa

2 touches
0 conflicts

0x533efb5c…354c

0x122c0d…e3fa

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

15 conflicts on slot 0xb0f2edf83f…4c4a2d

← previous block·next block →recent activity