Block #71,741,619

← previous blocknext block →recent activity

Analyzing

Block #71,741,619

30 transactions · 22 stateful · 2026-05-01 13:55:31 UTC

Parallelism

80/100

Blocked

50%

Avg conflicts / tx

0.73

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #71,741,619  ·  30 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

0x17606ba6…1b6e

0x754704…b603

10 touches
10 conflicts

0xd025d7d7…f05a

0x3bd359…433a

8 touches
6 conflicts

0x168d2c0f…79c6

0xd32edf…ff58

7 touches
6 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x846f77cd…a22c

0x065c9d…c394

5 touches
3 conflicts

0x00000000…0002

0x7e9d3a…9fda

4 touches
1 conflict

0x09000000…0001

0x000000…1000

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

10 conflicts on slot 0x17606ba612…ea1b6e

← previous block·next block →recent activity