← previous blocknext block →recent activity

Analyzing

Block #71,688,871

8 transactions · 7 stateful · 2026-05-01 08:04:12 UTC

Parallelism

75/100

Blocked

14%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,688,871  ·  8 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

0x50fe98a4…996f

0x065c9d…c394

4 touches
1 conflict

0x92f2bafc…f972

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xef7a182d…983c

0x065c9d…c394

3 touches
1 conflict

0x49f01d23…f75b

0x065c9d…c394

3 touches
1 conflict

0x504bdfff…a496

0x065c9d…c394

3 touches
1 conflict

0x508387de…c644

0x2a68ba…90c5

2 touches
0 conflicts

0xd74d5bed…5e7e

0x2a68ba…90c5

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 0x50fe98a4f6…8f996f

← previous block·next block →recent activity