Block #71,065,383

← previous blocknext block →recent activity

Analyzing

Block #71,065,383

6 transactions · 4 stateful · 2026-04-28 10:48:05 UTC

Parallelism

50/100

Blocked

50%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,065,383  ·  6 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xac9fc41c…e8bc

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0xe1ef7276…c14b

0x065c9d…c394

4 touches
1 conflict

0x199d2ea8…8cc3

0x065c9d…c394

4 touches
1 conflict

0x222ae6f9…c592

0x065c9d…c394

4 touches
1 conflict

0x5c5835f3…c89f

0x065c9d…c394

2 touches
1 conflict

0x37df13c7…d661

0x065c9d…c394

2 touches
1 conflict

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity