← previous blocknext block →recent activity

Analyzing

Block #71,643,419

21 transactions · 13 stateful · 2026-05-01 03:01:42 UTC

Parallelism

86/100

Blocked

31%

Avg conflicts / tx

0.24

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,643,419  ·  21 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x02962cf9…f59f

0xc8689a…ee79

4 touches
1 conflict

0x1a4b4152…0a08

0x33663b…4897

4 touches
1 conflict

0x2e2214a9…fe0d

0x33663b…4897

4 touches
1 conflict

0x3e4b8d9f…b8a7

0x33663b…4897

4 touches
1 conflict

0x50997ada…364d

0x33663b…4897

4 touches
1 conflict

0xc5564f8e…f4bf

0x33663b…4897

4 touches
1 conflict

0xf0f673fd…37a7

0x33663b…4897

4 touches
1 conflict

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity