Block #71,696,770

← previous blocknext block →recent activity

Analyzing

Block #71,696,770

9 transactions · 8 stateful · 2026-05-01 08:56:54 UTC

Parallelism

78/100

Blocked

13%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,696,770  ·  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

0xbd2c54b7…d86a

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x2e9c508d…4160

0x065c9d…c394

3 touches
1 conflict

0x58f70962…0c63

0x065c9d…c394

3 touches
1 conflict

0x0e445abc…cb91

0x065c9d…c394

3 touches
1 conflict

0xabe44c5a…1d8e

0x065c9d…c394

2 touches
0 conflicts

0xc2d82d4e…f545

0x065c9d…c394

2 touches
0 conflicts

0xda8ee426…738c

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 0xbd2c54b7f3…62d86a

← previous block·next block →recent activity