Block #71,743,019

← previous blocknext block →recent activity

Analyzing

Block #71,743,019

9 transactions · 9 stateful · 2026-05-01 14:04:51 UTC

Parallelism

78/100

Blocked

11%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,743,019  ·  9 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

0x4091f16e…a1c5

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x8a9d3969…a375

0x065c9d…c394

3 touches
1 conflict

0x8d948f5d…fa4d

0x065c9d…c394

3 touches
1 conflict

0x424022de…00f4

0x065c9d…c394

3 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

2 touches
0 conflicts

0x5f610cc8…6e32

0x065c9d…c394

2 touches
0 conflicts

0x508387de…c644

0x2a68ba…90c5

2 touches
0 conflicts

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 0x4091f16e43…39a1c5

← previous block·next block →recent activity