← previous blocknext block →recent activity

Analyzing

Block #71,243,205

10 transactions · 7 stateful · 2026-04-29 06:31:58 UTC

Parallelism

80/100

Blocked

14%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,243,205  ·  10 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

0xc6d89229…66c4

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x1543e463…37b4

0x065c9d…c394

3 touches
1 conflict

0x92444c5f…11b7

0x065c9d…c394

3 touches
1 conflict

0xbbe6dc0a…c67e

0x065c9d…c394

3 touches
1 conflict

0x8956cb26…42fa

0x73ada1…8be0

2 touches
0 conflicts

0x8956cb26…42fd

0x73ada1…8be0

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 0xc6d892293a…e866c4

← previous block·next block →recent activity