← previous blocknext block →recent activity

Analyzing

Block #71,703,543

10 transactions · 8 stateful · 2026-05-01 09:41:55 UTC

Parallelism

80/100

Blocked

13%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,703,543  ·  10 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

0x1ec9e06c…6d58

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x9a10ba98…d286

0x065c9d…c394

4 touches
1 conflict

0x1c2ab9d6…b6bd

0x065c9d…c394

3 touches
1 conflict

0x4a43315b…fd19

0x065c9d…c394

3 touches
1 conflict

0xd550b071…6803

0x065c9d…c394

2 touches
0 conflicts

0xe133d834…603b

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

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 0x1ec9e06cbf…ae6d58

← previous block·next block →recent activity