Block #71,742,368

← previous blocknext block →recent activity

Analyzing

Block #71,742,368

42 transactions · 22 stateful · 2026-05-01 14:00:30 UTC

Parallelism

88/100

Blocked

55%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #71,742,368  ·  42 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x8dfa31b0…da32

0xd32edf…ff58

9 touches
10 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x0dbf9688…c6cf

0xd18b7e…414b

6 touches
3 conflicts

0x4c32370c…3fbd

0x065c9d…c394

5 touches
3 conflicts

0x59ef13ba…2741

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x9e0e23b5…6910

0x34b655…2a6f

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

10 conflicts on slot 0x8dfa31b0f6…00da32

← previous block·next block →recent activity