← previous blocknext block →recent activity

Analyzing

Block #71,688,818

7 transactions · 7 stateful · 2026-05-01 08:03:51 UTC

Parallelism

57/100

Blocked

29%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,688,818  ·  7 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0x95a3897a…1336

0xd32edf…ff58

3 touches
1 conflict

0x09d5a55a…a751

0x065c9d…c394

3 touches
1 conflict

0x00f7e3b7…e015

0x188d58…ea8e

2 touches
0 conflicts

0x00f7e3b7…e016

0x188d58…ea8e

2 touches
0 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

2 touches
0 conflicts

0x01e7b865…6e6f

0x188d58…ea8e

2 touches
0 conflicts

0x729c91b8…9537

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: 0x2a68ba18…8e90c5

1 conflict on slot 0x92d610a6f9…379a40

← previous block·next block →recent activity