Block #71,683,655

← previous blocknext block →recent activity

Analyzing

Block #71,683,655

33 transactions · 26 stateful · 2026-05-01 07:29:32 UTC

Parallelism

82/100

Blocked

46%

Avg conflicts / tx

0.7

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #71,683,655  ·  33 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

0x81c20963…befd

0xd32edf…ff58

11 touches
15 conflicts

0x41755291…977f

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x0a6cb118…4ca7

0x1b6862…e19c

4 touches
1 conflict

0xd74d5bed…5e7e

0x2a68ba…90c5

4 touches
1 conflict

0x5639618d…6388

0x34b655…2a6f

4 touches
1 conflict

0x801a6e57…d85c

0x34b655…2a6f

4 touches
1 conflict

0xd6aabe89…92f5

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

15 conflicts on slot 0x81c20963e4…7cbefd

← previous block·next block →recent activity