Block #71,244,384

← previous blocknext block →recent activity

Analyzing

Block #71,244,384

6 transactions · 6 stateful · 2026-04-29 06:39:50 UTC

Parallelism

67/100

Blocked

17%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,244,384  ·  6 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

0xace514f7…0e98

0x065c9d…c394

4 touches
1 conflict

0xc7eb78e4…3e61

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xd250cec1…7fe2

0x065c9d…c394

2 touches
1 conflict

0x108fdbcb…3e58

0x065c9d…c394

2 touches
1 conflict

0x108fdbcb…3e59

0x065c9d…c394

2 touches
1 conflict

0xd250cec1…7fe3

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 0xace514f769…2e0e98

← previous block·next block →recent activity