Block #71,742,524

← previous blocknext block →recent activity

Analyzing

Block #71,742,524

21 transactions · 18 stateful · 2026-05-01 14:01:32 UTC

Parallelism

67/100

Blocked

56%

Avg conflicts / tx

1.24

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #71,742,524  ·  21 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x00000000…0002

0x7e9d3a…9fda

14 touches
21 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xffe431af…8faa

0x065c9d…c394

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x1f4df275…b8c0

0x065c9d…c394

3 touches
1 conflict

0xf096b1d6…ecc9

0x065c9d…c394

3 touches
1 conflict

0x68f8818a…de0b

0x065c9d…c394

3 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: 0x7e9d3a8a…4f9fda

21 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity