Block #71,701,215

← previous blocknext block →recent activity

Analyzing

Block #71,701,215

7 transactions · 7 stateful · 2026-05-01 09:26:25 UTC

Parallelism

71/100

Blocked

14%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,701,215  ·  7 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

0x26dd14d2…ccfe

0x065c9d…c394

4 touches
1 conflict

0xa220da03…b6f1

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x3d4bcef4…57e6

0x065c9d…c394

4 touches
1 conflict

0x41755291…977f

0x065c9d…c394

4 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

4 touches
1 conflict

0xf47828db…2a05

0x065c9d…c394

3 touches
1 conflict

0xfa970d1a…0dc6

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

1 conflict on slot 0x26dd14d273…b3ccfe

← previous block·next block →recent activity