Block #71,041,910

← previous blocknext block →recent activity

Analyzing

Block #71,041,910

5 transactions · 5 stateful · 2026-04-28 08:11:49 UTC

Parallelism

60/100

Blocked

20%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,041,910  ·  5 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

0x5ef20b9e…eb9b

0x065c9d…c394

4 touches
1 conflict

0x5b36896c…54db

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x58c3fa11…19e5

0x065c9d…c394

3 touches
1 conflict

0x02607699…40b5

0x065c9d…c394

3 touches
1 conflict

0x65a06171…97d0

0x065c9d…c394

2 touches
1 conflict

0x4a5854e6…1590

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

1 conflict on slot 0x5ef20b9e36…adeb9b

← previous block·next block →recent activity