← previous blocknext block →recent activity

Analyzing

Block #71,648,498

31 transactions · 22 stateful · 2026-05-01 03:35:26 UTC

Parallelism

84/100

Blocked

41%

Avg conflicts / tx

0.52

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #71,648,498  ·  31 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

0x2e9c3f55…8352

0xd32edf…ff58

7 touches
6 conflicts

0x01e7b865…6e6f

0x188d58…ea8e

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001b

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002b

0x1b6862…e19c

6 touches
3 conflicts

0xb0e4f69d…34e4

0x1b6862…e19c

6 touches
3 conflicts

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

6 conflicts on slot 0x2e9c3f555f…a28352

← previous block·next block →recent activity