Block #71,741,291

← previous blocknext block →recent activity

Analyzing

Block #71,741,291

39 transactions · 26 stateful · 2026-05-01 13:53:20 UTC

Parallelism

80/100

Blocked

42%

Avg conflicts / tx

0.79

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #71,741,291  ·  39 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x17606ba6…1b6e

0x754704…b603

12 touches
15 conflicts

0x67965b7b…7abe

0xd32edf…ff58

11 touches
15 conflicts

0xe75ce681…ba5f

0x188d58…ea8e

10 touches
10 conflicts

0x0dbf9688…c6cf

0xd18b7e…414b

8 touches
6 conflicts

0xe75ce681…ba60

0x188d58…ea8e

6 touches
3 conflicts

0xba5743c7…21c4

0x1b6862…e19c

4 touches
1 conflict

0xc824469a…641c

0x34b655…2a6f

4 touches
1 conflict

0x08f4c240…db35

0x754704…b603

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: 0x754704bc…afb603

15 conflicts on slot 0x17606ba612…ea1b6e

← previous block·next block →recent activity