Block #71,557,379

← previous blocknext block →recent activity

Analyzing

Block #71,557,379

12 transactions · 10 stateful · 2026-04-30 17:29:03 UTC

Parallelism

83/100

Blocked

10%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,557,379  ·  12 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

0x443a3e47…f4a4

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x2b86c38b…7e2b

0x065c9d…c394

3 touches
1 conflict

0x55f41584…03ca

0x065c9d…c394

3 touches
1 conflict

0x880aaeee…2fb1

0x065c9d…c394

3 touches
1 conflict

0x4cd41947…2611

0x065c9d…c394

3 touches
1 conflict

0x6b000777…7040

0x2a68ba…90c5

2 touches
0 conflicts

0x0b28bf77…e53a

0x34b655…2a6f

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 0x443a3e479f…3af4a4

← previous block·next block →recent activity