Block #72,571,246

← previous blocknext block →recent activity

Analyzing

Block #72,571,246

9 transactions · 8 stateful · 2026-05-05 10:07:36 UTC

Parallelism

67/100

Blocked

38%

Avg conflicts / tx

0.44

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,571,246  ·  9 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x2c96b35a…c63d

0x065c9d…c394

4 touches
1 conflict

0xa68d0ac3…a4eb

0x065c9d…c394

4 touches
1 conflict

0xb7de7106…69ef

0x065c9d…c394

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x42afe66d…b2f8

0x065c9d…c394

3 touches
1 conflict

0x51881c63…c4e5

0x065c9d…c394

2 touches
0 conflicts

0x570a189b…0b1c

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity