Block #71,741,547

← previous blocknext block →recent activity

Analyzing

Block #71,741,547

18 transactions · 11 stateful · 2026-05-01 13:55:02 UTC

Parallelism

89/100

Blocked

18%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,741,547  ·  18 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

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x37dbab74…4bc9

0x065c9d…c394

2 touches
0 conflicts

0xd10b36ee…7daf

0x065c9d…c394

2 touches
0 conflicts

0xd74d5bed…5e7e

0x2a68ba…90c5

2 touches
0 conflicts

0x0175b7a6…1db9

0x33663b…4897

2 touches
0 conflicts

0x0175b7a6…1dbc

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 0x5c8c6ab6f0…86dc36

← previous block·next block →recent activity