← previous blocknext block →recent activity

Analyzing

Block #72,425,412

6 transactions · 5 stateful · 2026-05-04 17:56:34 UTC

Parallelism

67/100

Blocked

20%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,425,412  ·  6 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

0x8fb893e6…a352

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x6bbd3e2f…b719

0x065c9d…c394

3 touches
1 conflict

0x603785b3…1e37

0x065c9d…c394

3 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

2 touches
0 conflicts

0x63f92fe3…7a71

0x065c9d…c394

2 touches
0 conflicts

0xb0efe789…748e

0x065c9d…c394

2 touches
0 conflicts

0xc5299629…5df0

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 0x8fb893e631…bba352

← previous block·next block →recent activity