← previous blocknext block →recent activity

Analyzing

Block #71,742,232

13 transactions · 11 stateful · 2026-05-01 13:59:36 UTC

Parallelism

77/100

Blocked

27%

Avg conflicts / tx

0.23

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,742,232  ·  13 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

0xfa503888…1168

0x065c9d…c394

4 touches
1 conflict

0xf3981be5…2c47

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xffe431af…8faa

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x83786629…bfb2

0xd32edf…ff58

3 touches
1 conflict

0x1b227524…f367

0x065c9d…c394

3 touches
1 conflict

0x3fa7ca4c…a524

0x065c9d…c394

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

1 conflict on slot 0xfa503888a1…f01168

← previous block·next block →recent activity