← previous blocknext block →recent activity

Analyzing

Block #71,744,313

17 transactions · 15 stateful · 2026-05-01 14:13:30 UTC

Parallelism

82/100

Blocked

40%

Avg conflicts / tx

0.47

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,744,313  ·  17 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

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x6513ae99…0852

0xd32edf…ff58

5 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x01e7b865…6e6d

0x188d58…ea8e

4 touches
1 conflict

0x00000000…0002

0x7e9d3a…9fda

4 touches
1 conflict

0x729c91b8…9538

0x188d58…ea8e

2 touches
0 conflicts

0x729c91b8…953a

0x188d58…ea8e

2 touches
0 conflicts

0xff5be972…9984

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

3 conflicts on slot 0x17606ba612…ea1b6e

← previous block·next block →recent activity