Block #71,742,643

← previous blocknext block →recent activity

Analyzing

Block #71,742,643

15 transactions · 12 stateful · 2026-05-01 14:02:20 UTC

Parallelism

87/100

Blocked

17%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,742,643  ·  15 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x532ac9c0…267c

0x065c9d…c394

4 touches
1 conflict

0x81fd68b0…3589

0x065c9d…c394

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x064cd89c…b5a2

0x065c9d…c394

3 touches
1 conflict

0x284e49ef…8a69

0x065c9d…c394

3 touches
1 conflict

0x76a9b911…8db7

0x065c9d…c394

3 touches
1 conflict

0x1e1bfb51…edef

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 0x532ac9c0cf…ed267c

← previous block·next block →recent activity