Block #71,704,002

← previous blocknext block →recent activity

Analyzing

Block #71,704,002

9 transactions · 8 stateful · 2026-05-01 09:44:59 UTC

Parallelism

78/100

Blocked

13%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,704,002  ·  9 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xebe62504…0f07

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x6007d354…efc1

0x065c9d…c394

3 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

2 touches
0 conflicts

0xd74d5bed…5e7e

0x2a68ba…90c5

2 touches
0 conflicts

0x1a4b4152…0a08

0x33663b…4897

2 touches
0 conflicts

0x2e2214a9…fe0d

0x33663b…4897

2 touches
0 conflicts

0x3e4b8d9f…b8a7

0x33663b…4897

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: 0x065c9d28…a9c394

1 conflict on slot 0xebe6250490…860f07

← previous block·next block →recent activity