Block #71,743,342

← previous blocknext block →recent activity

Analyzing

Block #71,743,342

11 transactions · 10 stateful · 2026-05-01 14:07:00 UTC

Parallelism

82/100

Blocked

10%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,743,342  ·  11 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

0x36f27b6c…6626

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xc7973a63…d20b

0x065c9d…c394

3 touches
1 conflict

0x5daa23ea…1724

0x065c9d…c394

3 touches
1 conflict

0x2f3123e8…25ee

0x065c9d…c394

3 touches
1 conflict

0x613a7157…07e8

0x065c9d…c394

2 touches
0 conflicts

0x76979235…f8db

0x065c9d…c394

2 touches
0 conflicts

0xda99ffda…527f

0x065c9d…c394

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 0x36f27b6c7b…8b6626

← previous block·next block →recent activity