Block #71,688,557

← previous blocknext block →recent activity

Analyzing

Block #71,688,557

20 transactions · 15 stateful · 2026-05-01 08:02:07 UTC

Parallelism

70/100

Blocked

40%

Avg conflicts / tx

0.8

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #71,688,557  ·  20 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

0x32a07bb0…b86f

0xd32edf…ff58

11 touches
15 conflicts

0x40d782a9…0701

0x065c9d…c394

3 touches
1 conflict

0x09000000…0001

0x000000…1000

2 touches
0 conflicts

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x09beabbc…065c

0x188d58…ea8e

2 touches
0 conflicts

0x09beabbc…065e

0x188d58…ea8e

2 touches
0 conflicts

0x46cb45de…a566

0x188d58…ea8e

2 touches
0 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

15 conflicts on slot 0x32a07bb02b…13b86f

← previous block·next block →recent activity