Block #71,243,295

← previous blocknext block →recent activity

Analyzing

Block #71,243,295

5 transactions · 3 stateful · 2026-04-29 06:32:34 UTC

Parallelism

60/100

Blocked

33%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x23bbc51d…668c

0x065c9d…c394

3 touches
1 conflict

0xdf38fee8…9bc4

0x065c9d…c394

3 touches
1 conflict

0xd3e71746…430f

0x065c9d…c394

3 touches
1 conflict

0x499d41bd…0ef3

0x065c9d…c394

3 touches
1 conflict

0x3a852b27…b0d4

0x065c9d…c394

2 touches
1 conflict

0x16083d9b…7ac8

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 0x0000000000…00003d

← previous block·next block →recent activity