← previous blocknext block →recent activity

Analyzing

Block #72,271,447

8 transactions · 7 stateful · 2026-05-04 00:49:20 UTC

Parallelism

75/100

Blocked

14%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,271,447  ·  8 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

0xbc70d921…d885

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x4ee695ed…2514

0x065c9d…c394

3 touches
1 conflict

0xf5012fa6…d9b9

0x065c9d…c394

3 touches
1 conflict

0xc2d82d4e…f545

0x065c9d…c394

2 touches
0 conflicts

0xd550b071…6803

0x065c9d…c394

2 touches
0 conflicts

0xee709f9c…f529

0x065c9d…c394

2 touches
0 conflicts

0x1c913164…5c2e

0x34b655…2a6f

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 0xbc70d921aa…66d885

← previous block·next block →recent activity