← previous blocknext block →recent activity

Analyzing

Block #72,395,221

8 transactions · 8 stateful · 2026-05-04 14:35:21 UTC

Parallelism

75/100

Blocked

13%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,395,221  ·  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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xe2c3c35b…a218

0x065c9d…c394

3 touches
1 conflict

0xdc09c6d0…a1fb

0x065c9d…c394

3 touches
1 conflict

0x4103e62a…c388

0x065c9d…c394

2 touches
0 conflicts

0x4a8b6c50…c6bc

0x065c9d…c394

2 touches
0 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

2 touches
0 conflicts

0x769bead8…3caa

0x065c9d…c394

2 touches
0 conflicts

0x810a6487…4fa3

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 0x0000000000…00003d

← previous block·next block →recent activity