Block #71,421,072

← previous blocknext block →recent activity

Analyzing

Block #71,421,072

11 transactions · 10 stateful · 2026-04-30 02:17:09 UTC

Parallelism

55/100

Blocked

50%

Avg conflicts / tx

1

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #71,421,072  ·  11 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xfcb7b8b2…ebb3

0x065c9d…c394

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x676f9f01…a8ac

0x34b655…2a6f

4 touches
1 conflict

0x4b61ebf9…49cb

0x065c9d…c394

4 touches
1 conflict

0x35060e21…aea8

0x065c9d…c394

3 touches
1 conflict

0x47bca935…1063

0x065c9d…c394

3 touches
1 conflict

0xee095ea8…2c4a

0x065c9d…c394

3 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

6 conflicts on slot 0xfcb7b8b239…6bebb3

← previous block·next block →recent activity